Re: defaulting 'svn log' to HEAD revision

Ben Collins-Sussman <sussman@collab.net> writes:

> 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.

As a long-time CVS user, I find this confusing, too. I guess I just
need to habitually update after a commit.

> True, but what can be done? The only solution is to make 'svn commit'
> automatically run 'svn update'. That's pretty awful.

Naive question: why is that bad?

Is it because the commit may have been partial? Otherwise, the WC is
now equivalent to the new HEAD, so updating it automatically makes
good sense.

-- 
  joq
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org