[Python-Dev] Hg: inter-branch workflow (original) (raw)
Barry Warsaw barry at python.org
Tue Mar 22 15:22:08 CET 2011
- Previous message: [Python-Dev] Hg: inter-branch workflow
- Next message: [Python-Dev] Hg: inter-branch workflow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 22, 2011, at 12:07 PM, Adrian Buehlmann wrote:
FWIW, Mercurial's "mainline" is the branch with the name 'default'. This branch name is reserved, and it implies that the head with the highest revision number from that branch will be checked out on 'hg clone'.
I think that's different than what John was describing, or perhaps Python's use of it has the effect of being different. IIUC, in Mercurial, within the default branch there's no clear "main line" of development assigned to a path within the DAG. All paths are created equal, so it's not possible to e.g. have log or bisect suppress one path containing feature sub-commits from the point of departure to the point of recombination (merge).
-Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20110322/8a550b7b/attachment.pgp>
- Previous message: [Python-Dev] Hg: inter-branch workflow
- Next message: [Python-Dev] Hg: inter-branch workflow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]