[python-committers] Why r69846 is not merged to "release26-maint"?
Brett Cannon
brett at python.org
Sat Jul 4 00:42:03 CEST 2009
More information about the python-committers mailing list
Sat Jul 4 00:42:03 CEST 2009
- Previous message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jul 3, 2009 at 15:34, Jesus Cea <jcea at jcea.es> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Please, somebody fix the reply-to :) > > A.M. Kuchling wrote: > > On Thu, Jul 02, 2009 at 02:34:38PM -0400, R. David Murray wrote: > >> On Fri, 3 Jul 2009 at 02:13, Anthony Baxter wrote: > >> Using svnmerge to commit to three branches in addition to trunk > >> is...painful. Because of the (lack of) speed. > > > > Should we push the Mercurial transition higher on the priority list, > > then? > > Please, do. I can't wait, and my activity is pretty low... (to change soon) > > I already asked for the mercurial transition status a few days ago, with > *no* (zero) answers. How is it going?. Can I help in any way?. It's being discussed on pyhon-dev. Dirkjan is the person to talk to if you want to help out. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20090703/1082eb48/attachment.htm>
- Previous message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list