git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How best to handle multiple-authorship commits in GIT?

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 3, 2012, 05:11 UTC
Message-ID
<7v1uqctsat.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAD-XujkVK=tOtmVS90U0KAutFZ55jxsHMKuuMppXOi-H6ZY=RQ@mail.gmail.com>
Valerie Aurora <valerie.aurora@gmail.com> writes:
Show 11 quoted lines
> 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.
Previous: Valerie AuroraNext: David Howells
Message 7 of 11 in “How best to handle multiple-authorship commits in GIT?”
  1. David HowellsFeb 2, 2012
  2. Frans KlaverFeb 2, 2012
  3. David HowellsFeb 2, 2012
  4. Valerie AuroraFeb 2, 2012
  5. David HowellsFeb 2, 2012
  6. Valerie AuroraFeb 3, 2012
  7. Junio C HamanoFeb 3, 2012
  8. David HowellsFeb 3, 2012
  9. Junio C HamanoFeb 3, 2012
  10. Valerie AuroraFeb 3, 2012
  11. Jakub NarebskiFeb 2, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.