On Tue, 20 Aug 2013 12:47:46 -0500 Tim Peters <tim.pet...@gmail.com> wrote: > > [Antoine] > > Ah, now I remember indeed: > > http://mail.python.org/pipermail/python-committers/2013-May/002580.html > > Which says: > > I asked about this on IRC and was told that 3.2 is now a > standalone branch like 2.7. Security fixes will be applied > by the release manager only, and Georg doesn't see any > point in null merging the commits. > > Isn't the point exactly the same as for all other "old-to-new branch" > null merges? That is, > > 1. So that 3.2 doesn't show up as an active branch under "hg branches"; and, > > 2. So that security fixes applied to the 3.2 branch can be easily > forward-ported to the 3.3 and default branches via no-hassle merges. > > What is gained by _not_ merging here? I don't see it.
Perhaps Georg doesn't like merges? ;-) I suppose what's gained is "one less command to type". Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
