"Patch by" was useful with Mercurial which didn't allow to store an author and a committer. Git now stores the author and the committer:
vstinner@apu$ git show --pretty=full 5b48dc638b7405fd9bde4d854bf477dfeaaddf44 --stat commit 5b48dc638b7405fd9bde4d854bf477dfeaaddf44 Author: Jonas Haag <jo...@lophus.org> Commit: Antoine Pitrou <pit...@free.fr> I'm not sure about added *manually* the author in the NEWS entry. I would prefer to have a generated page like https://thanks.rust-lang.org/ to limit the work of the reviewer (and of the author). My intent is not to hide the author of a contributor, but make contributions as simple as possible in Python, and to better "scale" our workflow. What do you think? Victor 2017-11-26 17:08 GMT+01:00 Mariatta Wijaya <mariatta.wij...@gmail.com>: > +1. > > Related question: Should the news entry include "Patch by <name>?". I > noticed some entries have this, some don't. Is there a rule? > > Thanks. > > > > _______________________________________________ > core-workflow mailing list -- core-workflow@python.org > To unsubscribe send an email to core-workflow-le...@python.org > https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct > _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-le...@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
