[Python-Dev] Hg: inter-branch workflow (original) (raw)
Barry Warsaw barry at python.org
Mon Mar 21 21:19:01 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 21, 2011, at 11:56 AM, Daniel Stutzbach wrote:
Keeping the repository clean makes it easier to use a bisection search to hunt down the introduction of a bug. If every developer's intermediate commits make it into the main repository, it's hard to go back to an older revision to test something, because many of the older revisions will be broken in some way.
So maybe this gets at my earlier question about rebase being cultural vs. technology, and the response about bzr having a strong sense of mainline where hg doesn't.
I don't use the bzr-bisect plugin too much, but I think by default it only follows commits on the main line, unless a bisect point is identified within a merge (i.e. side) line. So again, those merged intermediate changes are mostly ignored until they're needed.
-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/20110321/60eeb776/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 ]