From: josh@joshtriplett.org
To: Theodore Ts'o <tytso@mit.edu>
Cc: Tuncer Ayaz <tuncer.ayaz@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: co-authoring commits
Date: Wed, 17 Jun 2015 16:06:54 -0700 [thread overview]
Message-ID: <20150617230654.GA27206@cloud> (raw)
In-Reply-To: <20150617225224.GF4076@thunk.org>
On Wed, Jun 17, 2015 at 06:52:24PM -0400, Theodore Ts'o wrote:
> 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.
I've worked on many patches with another person in a shared screen
session, co-authoring a series of patches and commit messages in vim,
and writing an email in mutt. There were, ultimately, two people
deciding what to put in a commit and send to the maintainer. This is,
admittedly, unusual, but pair programming is not ridiculously uncommon.
> In that case, perhaps you could set the from field to a mailing list
> address.
The "From" field in email headers supports a list of comma-separated
addresses, just like To and Cc. Speaking from experience, this
more-or-less works with all the mail software we tried it with, with the
occasional program only displaying the first or last entry.
- Josh Triplett
next prev parent reply other threads:[~2015-06-17 23:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 19:52 co-authoring commits Tuncer Ayaz
2015-06-17 19:58 ` Junio C Hamano
2015-06-17 20:26 ` Tuncer Ayaz
2015-06-17 20:57 ` Junio C Hamano
2015-06-17 21:17 ` josh
2015-06-17 20:59 ` josh
2015-06-17 21:51 ` Junio C Hamano
2015-06-17 22:07 ` Tuncer Ayaz
2015-06-17 22:28 ` josh
2015-06-17 22:44 ` Junio C Hamano
2015-06-18 21:25 ` Jakub Narębski
2015-06-19 4:25 ` Jeff King
2015-06-19 18:02 ` Jakub Narębski
2015-06-17 22:52 ` Theodore Ts'o
2015-06-17 23:06 ` josh [this message]
2015-06-18 10:54 ` Jason Pyeron
2015-06-18 21:25 ` Tuncer Ayaz
2015-06-19 18:18 ` Jakub Narębski
2015-06-19 21:11 ` Tuncer Ayaz
2015-06-19 21:25 ` Jakub Narębski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150617230654.GA27206@cloud \
--to=josh@joshtriplett.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tuncer.ayaz@gmail.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).