Re: co-authoring commits

> On Wed, Jun 17, 2015 at 10:26:32PM +0200, Tuncer Ayaz wrote:
> > 
> > By allowing multiple authors, you don't have to decide who's the
> > primary author, as in such situations usually there is no primary at
> > all. I sometimes deliberately override the author when committing and
> > add myself just as another co-author in the commit message, but as
> > others have noted it would be really great if we can just specify
> > multiple authors.
> 
> Just recently, there a major thread on the IETF mailing list where
> IETF working group had drafts where people were listed as co-authors
> without their permission, and were upset that the fact that their name
> was added made it seem as if they agreed with the end product.  (i.e.,
> that they were endorsing the I-D).  So while adding formal coauthor
> might solves (a few) problems, it can also introduce others.
> 
> Ultimately there is one person who can decide which parts of the
> changes to put in the commit that gets sent to the maintainer.  So
> there *is* someone who is the primary author; the person who takes the
> final pass on the patch and then hits the send key.