On Jan 3, 2005, at 8:44 PM, Ben Collins-Sussman wrote:
>
> On Jan 3, 2005, at 5:58 PM, Vincent Lefevre wrote:
>>
>> IMHO, the real problem is not "svn log", but the fact that the working
>> copy is not automatically updated in some way to reflect the commit.
>>
>
> True, but what can be done? The only solution is to make 'svn commit'
> automatically run 'svn update'. That's pretty awful.
Actually I wouldn't mind that, with a switch to suppress the update in
the odd case where that might be needed. Running 'svn up' immediately
before and after a commit is something I always do anyway. A coworker
pointed out that the one thing he likes about SourceSafe is how files
are read-only in your working copy until you check them out, even if
you aren't using locking. The benefit to him is that when he goes to
modify a file and is forced to check it out it automatically gets the
latest version at that time. Saves him from some unnecessary and
possibly complex merging, but avoids the road block that locking
introduces.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 4 15:06:39 2005