Communication of CHANGES

Wow, I can't believe how much detail and philosophy people want to put
into the concept of locks. Let's keep this even simpler.

Nevermind locks. Let's just talk about files that are out of date.

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.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 25 16:58:10 2007