On Mon, Mar 7, 2011 at 1:44 AM, <s...@pobox.com> wrote: > > Georg> Yesterday's repository was still the test repository, now it's > Georg> the real one. You'll need to clone again. > > Thanks. > > I have a question about updates from cloned clones. Suppose I clone the > central repo then clone locally to get the 2.7 and 3.2 release branches: > > hg clone http://hg.python.org/cpython > hg clone cpython 3.2 > hg clone cpython 2.7 > > If I want to later update my maintenance branches to get any updates will it > suffice to just hg pull in my 2.7 and/or 3.2 directories or do I need to > pull in cpython first? I guess my question is, are these clones transitive?
Transitive. This is nice for the patch flow (fix in oldest, push, switch to next, merge, commit and push, etc, then only touch the central server for the final push of all branches), but it does you mean you need to follow the reverse order when grabbing changes from the central repository. Being slightly out of date is far less of a drama than it used to be, though. 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
