[python-committers] Why r69846 is not merged to "release26-maint"?
Nick Coghlan
ncoghlan at gmail.com
Thu Jul 2 23:13:03 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 23:13: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 ]
Mark Dickinson wrote: > Speaking as one of the people who occasionally remembers to backport > to 3.0 (though clearly I failed with r69846), it wouldn't bother me at all > if there were no 3.0.2. I can't speak for any of the other backporters, of > course. > > I'm not really sure who 3.0.2 would be useful for. I agree with what Mark has said above (it also means I can just svn switch my 3.0 checkout to 3.1 rather than adding a 5th local working copy). Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
- 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