[Python-Dev] GitHub migration scheduled for Friday

Brett Cannon brett at python.org
Wed Feb 8 17:42:44 EST 2017

On Wed, 8 Feb 2017 at 13:33 Victor Stinner <victor.stinner at gmail.com> wrote:

> 2017-02-08 21:32 GMT+01:00 Terry Reedy <tjreedy at udel.edu>:
> > Many patches have multiple authors. Does the 'author' field allow that?
> > Often, the committer adds missing chunks or rewrites the work with
> various
> > degrees of editing.  Sometimes a read a patch for the idea and then start
> > fresh with the actual code.  An acknowledgement in the news entry can be
> > written different ways to reflect the situation.
> In my experience, the common case is two "authors": the initial patch
> autor, and the core dev who makes minor changes like filling Misc/NEWS
> and adjust some parts of the code. If changes are minor, there is no
> need to elaborate. But if changes are non straightforward, they can be
> listed in the commit messages.
> If a patch has more author, you have to pick the name, decide which
> author helped the most, and add the other authors in the commit
> message.
> Using GitHub, it will become easier to use patch series, and so
> smaller changes. Each change may have a different author :-D

Don't forget we are doing squash merges, so if a PR has multiple authors
then the author information won't carry forward in git (I don't know if
GitHub has custom logic to work around this).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170208/6c62e72f/attachment.html>

More information about the Python-Dev mailing list