confusing pull -u behavior

[Mads Kiilerich]

Neal Becker wrote, On 03/12/2009 02:49 PM:
> Now try again
> $ hg pull -u
> pulling from ssh://nbecker1/scma-ldpc1_9-fixed
> searching for changes
> no changes found
>
> $ ls -l run-tests-aci.py
> ls: cannot access run-tests-aci.py: No such file or directory
>
> Oops, this is what I need:
> $ hg update
> 4 files updated, 0 files merged, 0 files removed, 0 files unresolved
>
> I've made this mistake more than once now, is there a better way?
>   


Yes, pull -u is a very convenient combination of two commands, and it is 
clearly documented what it is intended to do, and that is exactly what 
it does. But very often I want something else. What is "missing" is a 
_different_ combination of the pull and the update.

But ... why should that be built in? A better solution is to use the 
shell to combine Mercurial commands. In this example "hg pull;hg up" is 
what is meant, so why not just use that instead?

/Mads


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3435 bytes
Desc: S/MIME Cryptographic Signature
Url : http://selenic.com/pipermail/mercurial/attachments/20090313/15185738/attachment.bin