On Nov 27, 2007 2:45 PM, Harvey, Edward <Edward.Harvey@patni.com> wrote:
> > I think he simply meant the goal is to display the same information
> > ... faster. The original idea seemed to suggest that you could skip
> > checking specific items once you know there is a newer version in the
> > repository. IOW, if revision 5 is in the WC, you run svn status -u
> > and find out there is now a revision 10 of the same item, then if the
> > user runs the option again there is no need to check that item again,
> > because you already know there is a newer version.
>
> Again, I am not suggesting changing anything at all with regards to the
> performance or output of "svn status" or "svn status -u" The goal of
> remembering a previous "svn status -u" is NOT performance boost. The
> goal is feature enhancement.
>
> I am suggesting that gui clients, such as tortoise, could (if the user
> wants it) display an icon indicating that a particular file is already
> known to be out of date. This will discourage but not prevent a user
> from editing the file until he/she first updates that file.
>
> At present, gui clients cannot display a "file is out of date" icon,
> because there's no way to remember the status when the client previously
> checked for updates.
Of course there is a way. The GUI client can cache the information
itself. TortoiseSVN already has an elaborate cache that drives these
badges. Subclipse has a cache that does exactly this too, although we
do not persist it on shutdown.
I doubt TortoiseSVN would use this feature regardless because the last
I knew they were severely limited by Windows in the number of badges
it can use.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 27 20:54:25 2007