[Python-Dev] hg pull failed

[Adrian Buehlmann]

On 2011-03-06 20:09, "Martin v. Löwis" wrote:
>>> So, when I cloned, I should have done something like this:
>>>
>>>      hg clone http://hg.python.org/cpython
>>>      hg clone cpython 3.2
>>>      hg clone 3.2 3.1
>>>      hg clone cpython 2.7
>>>      hg clone 2.7 2.6
>>>      hg clone 2.6 2.5
>>>      hg clone 2.5 2.4
>>>
>>> instead of cloning everything from cpython, right?
>>
>> You can still change the "default" entries in .hg/hgrc to point to
>> your desired default location.  That's the *only* thing that changes
>> depending on where you clone from.
> 
> What I often do is to add another line (below default=, or in
> ~/.hgrc), so I can do
> 
> hg pull # pulls from my local copy
> hg push pydotorg # pushes directly into the remote directory
> 

Not sure if it fits in your specific case you mention here, but
Mercurial has a reserved path alias name "default-push" with special
meaning:

'hg push' pushes to

(1) the path defined as default-push under [paths] in .hg/hgrc
(2) if default-push is not defined, to the default path
(3) if neither is defined, the command aborts with an error message

'hg pull' always pulls from the default path (default-push doesn't
matter for pull).

(Same for the outgoing/incoming commands.)

http://selenic.com/repo/hg/help/paths