[Python-Dev] hg pull failed
Georg Brandl
g.brandl at gmx.net
Sun Mar 6 18:47:31 CET 2011
More information about the Python-Dev mailing list
Sun Mar 6 18:47:31 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:39, skip at pobox.com wrote: > > Nick> Transitive. This is nice for the patch flow (fix in oldest, push, > Nick> switch to next, merge, commit and push, etc, then only touch the > Nick> central server for the final push of all branches), but it does > Nick> you mean you need to follow the reverse order when grabbing > Nick> changes from the central repository. > > Ummm, push from where to where? Are you assuming some relationship between > my sandboxes? "push" sounds to me like pushing my changes to the central > repository. That's not what I would want to do. Any transfer of changesets between repositories is (depending on the direction) called a pull or push, and performed using the hg commands of the same name. The relationship between local clones is as symmetric as the one between a local and a remote clone. 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