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

[Jesus Cea]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anthony Baxter wrote:
> Speaking as a past release manager, the reason that things like that
> didn't get merged is because... drumroll... no-one merged them.

Ughhh. This is actually a good reason to migrate to mercurial, were
merges are painless :-).

> 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.

I already have the checkouts for the maintained branches. I will try to
merge that patch, although it is old and will probably generate a ton of
conflicts. Let's see...

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBSkzO+5lgi5GaxT1NAQLUFwP/QfS/U20tSS1Xd6P9nm3V2OADxOs9aFSK
TEpluTRSZ3o3E8GoXGjx1BBns3rffM7+VSIIvnlzujzTF9r4nUxy26TNjDKBnZ9j
aByQAtJVY2FY3nYYIxZ1SJn1w4HWBtueckZV5fCZmMRpLWEQSwfbVFIq3+6IHwC2
xCVByx9x+yI=
=SvWZ
-----END PGP SIGNATURE-----