[issue11795] Better core dev guidelines for committing submitted patches

R. David Murray added the comment: Note that the older tradition was to *not* mention the contributor in NEWS (NEWS was just technical notes), but to mention them in the checkin message (and What's New, for things that make the What's New cut). However, since we can't edit checkin messages p

[issue11795] Better core dev guidelines for committing submitted patches

Changes by Nick Coghlan : -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___

[issue11795] Better core dev guidelines for committing submitted patches

Nick Coghlan added the comment: Enhanced committer guidelines: http://hg.python.org/devguide/rev/774fb024b152 -- ___ Python tracker ___ _

[issue11795] Better core dev guidelines for committing submitted patches

Éric Araujo added the comment: +1 -- nosy: +eric.araujo versions: +3rd party ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11795] Better core dev guidelines for committing submitted patches

Terry J. Reedy added the comment: I had some of the same questions, so I agree this would be a good addition. -- nosy: +terry.reedy stage: -> needs patch ___ Python tracker ___

[issue11795] Better core dev guidelines for committing submitted patches

Changes by Alexander Belopolsky : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue11795] Better core dev guidelines for committing submitted patches

Changes by Nadeem Vawda : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue11795] Better core dev guidelines for committing submitted patches

New submission from Nick Coghlan : Based on a core-mentoring thread, a couple more points for: http://docs.python.org/devguide/committing.html#handling-other-s-code Attribution: - add to Misc/ACKS if they aren't already there (and didn't add themselves in their patch) - mention "Patch by " in t