[python-committers] Do people prefer pushing feature repos or one massive patch?

Brett Cannon bcannon at gmail.com
Wed Apr 1 19:50:52 CEST 2015


On Wed, Apr 1, 2015 at 12:56 PM Victor Stinner <victor.stinner at gmail.com>
wrote:

> If you choose to merge, I would prefer that you rebase your changes
> before to avoid multiple merges. IMO the best to avoid merges at all
> :-)
>

It's sounding like one massive patch is the best option for people.


>
> Did someone review your large change?
>

It just went up earlier today, so no. It's actually a fairly simple patch,
it's just there was a lot of files involved that had some comment
mentioning .pyo files.

-Brett


>
> Victor
>
> 2015-04-01 18:09 GMT+02:00 Brett Cannon <bcannon at gmail.com>:
> > 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?
> >
> > _______________________________________________
> > python-committers mailing list
> > python-committers at python.org
> > https://mail.python.org/mailman/listinfo/python-committers
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20150401/ea985cf3/attachment.html>


More information about the python-committers mailing list