From: Junio C Hamano <gitster@pobox.com>
To: Valerie Aurora <valerie.aurora@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: How best to handle multiple-authorship commits in GIT?
Date: Thu, 02 Feb 2012 21:11:22 -0800 [thread overview]
Message-ID: <7v1uqctsat.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAD-XujkVK=tOtmVS90U0KAutFZ55jxsHMKuuMppXOi-H6ZY=RQ@mail.gmail.com> (Valerie Aurora's message of "Thu, 2 Feb 2012 18:18:50 -0800")
Valerie Aurora <valerie.aurora@gmail.com> writes:
> And Rusty's practice as of a year or two ago is for "minor mods" to a
> patch, to leave the authorship the same, and add a Signed-off-by:
>
> Signed-off-by: Some Upstream Author
> Signed-off-by: Maintainer or Merger (rewrote error handling)
>
> And for a complete (meaningful) rewrite such as David has done, he
> changes the commit authorship and adds a Signed-off-by for the
> original author.
>
> That's existing guidelines and practice.
All sounds very sensible. Thanks for a summary.
next prev parent reply other threads:[~2012-02-03 5:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 12:25 How best to handle multiple-authorship commits in GIT? David Howells
2012-02-02 13:41 ` Frans Klaver
2012-02-02 18:00 ` Valerie Aurora
2012-02-02 19:57 ` Jakub Narebski
2012-02-02 18:36 ` David Howells
2012-02-03 2:18 ` Valerie Aurora
2012-02-03 5:11 ` Junio C Hamano [this message]
2012-02-03 13:47 ` David Howells
2012-02-03 18:27 ` Junio C Hamano
2012-02-03 19:49 ` Valerie Aurora
2012-02-02 20:33 ` David Howells
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=7v1uqctsat.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dhowells@redhat.com \
--cc=git@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=valerie.aurora@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).