[python-committers] Why r69846 is not merged to "release26-maint"?
Benjamin Peterson
benjamin at python.org
Thu Jul 2 16:43:19 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 16:43:19 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 ]
2009/7/2 Jesus Cea <jcea at jcea.es>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have found a few flaws in 2.6 documentation. I was going to correct > them when I found they are already solved in trunk in r69846, done by > mark.dickinson in february. > > Is there any reason for that commit not to be merged to 2.6 branch?. Am > I missing anything?. People usually don't merge documentation changes because it's more trouble than it's worth. You can merge that one, though. -- Regards, Benjamin
- 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