[python-committers] Why r69846 is not merged to "release26-maint"?
Brett Cannon
brett at python.org
Thu Jul 2 21:03:03 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 21:03: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 Thu, Jul 2, 2009 at 11:46, A.M. Kuchling <amk at amk.ca> 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? I thought it was already high on the priority list and that Dirkjan was actively working on the transition. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20090702/c0a8feba/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