Nick Coghlan ncoghlan at gmail.com
Mon Mar 7 01:14:30 CET 2011

• Previous message: [Python-Dev] hg pull failed
• Next message: [Python-Dev] hg pull failed
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Mon, Mar 7, 2011 at 5:36 AM, Adrian Buehlmann <adrian at cadifra.com> wrote:
> 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).

Oh, so I can split the lookup so a bare "hg pull" comes directly from
pydotorg, while having a bare "hg push" follow the transitive links
between my local clones? Very interesting!

I'll try the fully transitive workflow for now, though and see how I like it.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• Previous message: [Python-Dev] hg pull failed
• Next message: [Python-Dev] hg pull failed
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list