From: Theodore Ts'o <tytso@mit.edu>
To: Tuncer Ayaz <tuncer.ayaz@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Josh Triplett <josh@joshtriplett.org>
Subject: Re: co-authoring commits
Date: Wed, 17 Jun 2015 18:52:24 -0400 [thread overview]
Message-ID: <20150617225224.GF4076@thunk.org> (raw)
In-Reply-To: <CAOvwQ4j2bjR1jnLVyZbw1OCE=xQxbCEFGKcK1bpuv1K3s_Y2EQ@mail.gmail.com>
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.
One could imagine some frankly, quite rare example where there is a
team of people who votes on each commit before it gets sent out and
where everyone is equal and there is no hierarchy. In that case,
perhaps you could set the from field to a mailing list address. But
honestly, how often is that *all* of the authors are completely
equal[1]?
In my personal practice, if I make significant changes to a patch, I
will indeed simply change the submitter, and then give credit the
original author. This is the case where I'm essentially saying, "Bob
did a lot of work, but I made a bunch of changes, so if things break
horribly, blame *me*, not Bob".
Alternatively, if I just need to make a few cosmetic changes to
Alice's patch (i.e., fix white spaces, correct spelling, change the
commit description so it's validly parsable and understandable
English, etc.), I'll just add a comment in square brackets indicating
what changes I made before I committed the change. This seems to work
just fine, and I don't think we should try to fix something that isn't
broken.
- Ted
[1] Gilbert and Sullivan attacked this notion is a commedic way in
"The Gondoliers"; especially in the songs "Replying we sing as one
individual" and "There Lived a King":
https://www.youtube.com/watch?v=YD0dgXTQ3K0
https://www.youtube.com/watch?v=oSaVdqcDgZc
next prev parent reply other threads:[~2015-06-17 22:52 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 [this message]
2015-06-17 23:06 ` josh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150617225224.GF4076@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=josh@joshtriplett.org \
--cc=tuncer.ayaz@gmail.com \
/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.
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 NNTP newsgroup(s).