Ben Collins-Sussman wrote:
>
> On Jan 3, 2005, at 5:58 PM, Vincent Lefevre wrote:
>
>> On 2005-01-02 21:48:17 -0600, kfogel@collab.net wrote:
>>
>>> Many users (including me) are periodically confused and/or
>>> annoyed by the fact that 'svn log' defaults to the working copy
>>> at BASE, instead of at HEAD. That is:
>>>
>>> $ svn commit -m "Commit a new revision." [...] Committed revision
>>> 245. $ svn log [... r245 is not shown, because it's too recent
>>> ...] $
>>
>>
>> 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.
Personally, I'd like to see another command that was the equivalent of
'commit and update' ('cu', as someone else suggested on the dev@ list).
I think it would not only hope those people who aren't really used to
mixed revision working copies, and it would help my team, especially
since we never make use of the mixed-revision features. Also, scripting
it is *a lot* more painful in Windows, and most of them use TortoiseSVN,
which is impossible to script.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 5 02:14:05 2005