While looking at the diffs between the 261 release tags and the 26 branch, I
noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6 sections.
I moved all of these to 2.6.2, after checking some of them, and found all of the
checked ones be backported after the 2.6.1 release. Is there anything what could
be done to avoid these wrong merges?
I plan to check the items on the 3.0 branch soon.
Matthias
The py3k branch is now frozen for 3.1 final to be tagged. If you need
to contact me, I will be watching my inbox and on Freenode IRC
#python-dev. The tree will be frozen for about a day, so binaries can
be built.
--
Regards,
Benjamin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, everybody. I have read PEP 385, but there is no time schedule there,
and I was wondering how is the migration done.
Any idea of when can we use Mercurial to do our contributions?.
- --
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
jabber / xmpp:jcea@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
iQCVAwUBSjuiSplgi5GaxT1NAQI7igP9E2kai8uTn2E8PiEiC92UtYToEe9wcRi/
M2f7dBuOXK3zsLlz6xUVJnphP67DtXiFStpi1dTZXGS5H3Na8WqtW3gggOfbrQH3
kaB3mzOfhWVG8H85umhVR3qsUouz3pChIyK1lMVbHcFiHcHuE/pf2OaZJOfHS3jw
g1WCCpE0068=
=UhI3
-----END PGP SIGNATURE-----
