[python-committers] Do people prefer pushing feature repos or one massive patch?
Brett Cannon
bcannon at gmail.com
Wed Apr 1 18:39:46 CEST 2015
More information about the python-committers mailing list
Wed Apr 1 18:39:46 CEST 2015
- Previous message (by thread): [python-committers] Do people prefer pushing feature repos or one massive patch?
- Next message (by thread): [python-committers] Do people prefer pushing feature repos or one massive patch?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Apr 1, 2015 at 12:38 PM Benjamin Peterson <benjamin at python.org> wrote: > > > On Wed, Apr 1, 2015, at 12:09, Brett Cannon wrote: > > The implementation for PEP 488 is basically done (sans Windows installer > > stuff). I did the work in a features repo at > > https://hg.python.org/features/pep-488/ . Once I have addressed reviewer > > comments at http://bugs.python.org/issue23731 , would people prefer I > > simply push the features repo to hg.python.org/cpython and have the more > > granular history but have various "merge default" commits, or would > > people > > rather I do one massive commit? > > I tend to prefer the one massive commit especially if there's a lot of > "in progress" commits in the branch. It makes for cleaner and > more-transactional history. > The commits are actually self-contained so that's not an issue in this case. But I do understand the desire for the easy rollback potential. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20150401/ee3fef64/attachment.html>
- Previous message (by thread): [python-committers] Do people prefer pushing feature repos or one massive patch?
- Next message (by thread): [python-committers] Do people prefer pushing feature repos or one massive patch?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list