> Are you asking for the info to be cached, as in made available
> offline? Or do you just want a better or clearer interface for
getting
> lock information?
It's not quite like "made available offline," because there's really no
such thing as "online" or "offline" with subversion. And there's no
problem with the "Check for Modifications" or "svn status -u"
interfaces. And there's no problem with the "svn:needs-lock" property.
Each one does a decent job at what it does.
I'm really talking about something new.
In the present implementation, the gui clients can only show you
information about your local modifications. The only way to check for
somebody else's modifications is to "Check for Modifications" and if you
do, the results will be instantly forgotten once the check is finished.
Suppose Harry checks for modifications on the root of a tree, and he
sees that several files were modified by some other users. But harry
doesn't want to do an update yet. It would be really useful for him to
browse into that tree, and see that some files are out of date. If the
gui client could remember the most recent results of "check for
modifications." Likewise if some other user locked a file, most likely
a change commit to that file is imminent, so Harry should treat the
locked file the same as he treats a file that's already out of date. So
both "out of date" and "repository lock" would be useful information for
Harry to see in his gui client.
Better yet, if Harry could check for modifications on a periodic basis,
on the root of a tree. It's simply an improvement of communications.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 21 18:33:12 2007