Re: defaulting 'svn log' to HEAD revision

Scott Palmer <scott.palmer@2connected.org> writes:

> On Jan 4, 2005, at 9:29 AM, Jack O'Quin wrote:
>
>> Ben Collins-Sussman <sussman@collab.net> writes:
>>
>> 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,
>
> NOT true. WC is rev 1 another developer has committed rev 2 (but
> doesn't change the same files as you) check in WC to make rev 3 the WC
> is NOT HEAD because it doesn't have the changes from rev 2
>
>> so updating it automatically makes good sense.
>
> It makes sense because you probably want the changes from rev 2 using
> my example above.

Yes. Generally, I want to...

  $ svn update
  $ make
  $ test
  $ svn status # make sure there are no new changes
  $ svn commit
  $ svn update # because my WC is now at the new level

I want to avoid partial updates, because then the new HEAD would not
reflect the version I tested.

It's only the last step that seems strange when moving from CVS.

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