[Python-Dev] Hg: inter-branch workflow
Antoine Pitrou
solipsis at pitrou.net
Mon Mar 21 21:53:26 CET 2011
More information about the Python-Dev mailing list
Mon Mar 21 21:53:26 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 Mon, 21 Mar 2011 16:33:31 -0400 Barry Warsaw <barry at python.org> wrote: > Each of those would be > represented by a changeset in my local line of development, and by a side > branch in the mainline DAG once my merge is completed. You might want to dig > into that sideline to see if indeed I addressed the issues in your second > review of my code. If we have to manually collapse changesets at feature > branch merge time, you can't do that. I'd rather take a look at the final aggregate patch to see if it looks correct, actually. It's easy to have incremental changes which look good but lead to a questionable patch in the end. Better to review it in aggregate, IMO. Regards Antoine.
- Previous message: [Python-Dev] Hg: inter-branch workflow
- Next message: [Python-Dev] Hg: inter-branch workflow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list