[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Communication of CHANGES

From: Jamie A Lawrence <jal_at_clueinc.net>
Date: 2007-11-25 22:53:16 CET

On Nov 25, 2007, at 4:26 PM, Karl Fogel wrote:
> This is an interesting idea, and is obviously feasible. Once a file
> is known to be out-of-date, it remains so until the next update.
> There's no reason we couldn't cache that fact.
> However, could you spell out the advantage to be gained from this?

Not the OP, but the main one I can think of is for clients like tortoise
that integrate with a GUI, so that icons could reflect current status
a network roundtrip and subsequent potential delay. I used to work on a
project where the repository was on a very, very slow remote link, to
the point
where `svn status` was in the Landau O(get-a-cup-of-coffee) class of

I don't see much to be gained for command line users like myself,
for those who like ANSI colors for different types of files, there is
something clever that could be done to make out of date files yellow
or blink
or something [shudders].


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 26 19:33:13 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.