[Python-Dev] hg pull failed
Georg Brandl
g.brandl at gmx.net
Sun Mar 6 19:01:59 CET 2011
More information about the Python-Dev mailing list
Sun Mar 6 19:01:59 CET 2011
- Previous message: [Python-Dev] hg pull failed
- Next message: [Python-Dev] hg pull failed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 06.03.2011 18:45, skip at pobox.com wrote: > > Nick> Given the recommended workflow in the devguide (i.e. when forward > Nick> porting bug fixes, update all public branches in a single push), > Nick> keeping the transitive connections between local clones is > Nick> probably a good idea. It also means that we can do the full > Nick> porting workflow even when offline. > > 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. Georg
- 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