[Python-Dev] Non-code changes on "old" branches
Terry Reedy
tjreedy at udel.edu
Thu Mar 31 14:56:54 CEST 2011
More information about the Python-Dev mailing list
Thu Mar 31 14:56:54 CEST 2011
- Previous message: [Python-Dev] Non-code changes on "old" branches
- Next message: [Python-Dev] EuroPython 2011: call for paper is ending - Please spread the word!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/31/2011 12:31 AM, Mark Hammond wrote: > Hi, > There are a couple of changes I'd like to make and would like some > guidance on policy: > > http://bugs.python.org/issue6498 is a documentation bug which exists in > Python 2.6 and later. The patch in that bug touches the docs and a > comment in one source file. Is it acceptable to push that change to the > 2.6 branch, or should I start with 2.7? I believe no, not 2.6, lest you be asked to revert. Start with 2.7 -- Terry Jan Reedy
- Previous message: [Python-Dev] Non-code changes on "old" branches
- Next message: [Python-Dev] EuroPython 2011: call for paper is ending - Please spread the word!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list