Home Original page

[python-committers] Why r69846 is not merged to "release26-maint"?

Anthony Baxter anthonybaxter at gmail.com
Thu Jul 2 16:58:24 CEST 2009 
Speaking as a past release manager, the reason that things like that didn't
get merged is because... drumroll... no-one merged them.
It's another tree to checkout and patch. Personally, I was always of the
belief that if someone wanted to fix docs (or comments, or other things like
that) in a maintenance branch, more power to them.



On Fri, Jul 3, 2009 at 12:43 AM, Benjamin Peterson <benjamin at python.org>wrote:

> 2009/7/2 Jesus Cea <jcea at jcea.es>:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I have found a few flaws in 2.6 documentation. I was going to correct
> > them when I found they are already solved in trunk in r69846, done by
> > mark.dickinson in february.
> >
> > Is there any reason for that commit not to be merged to 2.6 branch?. Am
> > I missing anything?.
>
> People usually don't merge documentation changes because it's more
> trouble than it's worth. You can merge that one, though.
>
>
>
> --
> Regards,
> Benjamin
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> http://mail.python.org/mailman/listinfo/python-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20090703/1b65039e/attachment.htm>
More information about the python-committers mailing list