[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: Bruce Wilson <b-svn_at_toomuchblue.com>
Date: 2007-11-26 23:32:41 CET

Les Mikesell wrote:
> Harvey, Edward wrote:
>> In fact, I can't imagine any use for the cached information on a command
>> prompt. The advantage is gained by GUI clients. For example,
>> TortoiseSVN could update the icon of somefile.txt if it knows that
>> somefile.txt is already out of date. This would discourage (but not
>> prevent) the user from editing that file unless they update first.
> And if the file doesn't have a cached out of date symbol? Won't that
> same user expect it to not be out of date?
But what does that buy them? They still have to meet the same
requirements when they commit. If the changes are non-overlapping, the
commit may still be trivial. If all appears well but there's a change by
the time they commit, they'll still have to deal with it.

Likewise, if a file has been rolled back to match the user's base-rev, a
false "file is out of date" flag isn't going to hurt anything.

svn status -u can give you the same false feeling of comfort/anxiety.
The advantage is offline and/or cached access to this information.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 26 23:33:18 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.