Message166355
| Author |
chris.jerdonek |
| Recipients |
chris.jerdonek, docs@python, eric.araujo, ezio.melotti, georg.brandl, jcea, loewis, meador.inge, pitrou, rhettinger, serhiy.storchaka |
| Date |
2012年07月25日.05:58:17 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1343195898.84.0.889400296668.issue15439@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Okay, thanks for clarifying. Then I have no strong opinion.
However, if Doc/ACKS.txt is retained, then I think the Dev Guide should mention Doc/ACKS.txt just as it mentions Misc/ACKS:
http://docs.python.org/devguide/patch.html#preparation
And it should include instructions for when to update which files, and the patchcheck script should be suitably modified. With only ~230 names versus Misc/ACKS's ~1160 , I'm surprised that Doc/ACKS.txt does not have more names -- especially given that it's not uncommon for documentation changes to accompany code changes (or so one might think). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年07月25日 05:58:18 | chris.jerdonek | set | recipients:
+ chris.jerdonek, loewis, georg.brandl, rhettinger, jcea, pitrou, ezio.melotti, eric.araujo, meador.inge, docs@python, serhiy.storchaka |
| 2012年07月25日 05:58:18 | chris.jerdonek | set | messageid: <1343195898.84.0.889400296668.issue15439@psf.upfronthosting.co.za> |
| 2012年07月25日 05:58:18 | chris.jerdonek | link | issue15439 messages |
| 2012年07月25日 05:58:17 | chris.jerdonek | create |
|