[python-committers] Why r69846 is not merged to "release26-maint"?
R. David Murray
rdmurray at bitdance.com
Thu Jul 2 17:06:50 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 17:06:50 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, 3 Jul 2009 at 00:58, 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. > 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. What I do is accumulate a list of doc fixes I've made, and when the list gets to some undefined size or age, I merge them all in one svnmerge batch. I think Georg does something similar. --David
- 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