On Mon, Mar 7, 2011 at 2:07 AM, Georg Brandl <g.bra...@gmx.net> wrote: > If you don't change repo configuration after these commands, "hg pull" in the > 3.2 repo will pull from the local cpython repo. I'd advise to set the > "default" > entry in each of the clones' .hg/hgrc file to http://hg.python.org/cpython > (as a committer you should be using ssh://h...@hg.python.org/cpython BTW). > > This way, "hg push" and "hg pull" communicate with the remote repo. You can > still exchange commits with the other local clones by using, for example, > "hg push ../3.2". (You can also add another entry in the .hgrc's [paths] > section if you want to give nicknames to these path names).
Given the recommended workflow in the devguide (i.e. when forward porting bug fixes, update all public branches in a single push), keeping the transitive connections between local clones is probably a good idea. It also means that we can do the full porting workflow even when offline. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
