[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: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-11-25 22:26:01 CET

"Harvey, Edward" <Edward.Harvey@patni.com> writes:
> When a user does "svn status -u" (or in tortoise "Check for
> Modifications/Check Repository") the client will check the server to see
> what's changed. If some file is now known to be out-of-date, it would
> be useful for svn to cache that information locally, so the gui client
> could mark that file as "out of date" without having to re-poll the
> server.
> Optionally, users could even schedule a periodic "svn status -u" if they
> wanted to.
> This would need to be "harmlessly cached" meaning it does not interfere
> with the behavior of any functions that already exist in subversion.
> Does it sound like a good idea to locally cache, in the .svn directory,
> "file is out of date" information? I think so.

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?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 25 22:26:27 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.