git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download mbox.gz: |
* recognizing multiple authors for a patch?
@ 2008-06-05  8:27 99% Brian Swetland
  0 siblings, 0 replies; 1+ results
From: Brian Swetland @ 2008-06-05  8:27 UTC (permalink / raw)
  To: git


Nicolas Pitre said, in the thread on the "preserve the committer" patch:
> I think this is against the purpose of the committer field to preserve
> it from a commit that was not made by you.  What really really has to be
> preserved is the author field of course.  But attributing commit action
> to someone else than yourself when you are the one reorganizing commits
> is misrepresentation.

Which reminds me of a longstanding question I have -- how best to
represent patches which have multiple authors?

I'm submitted patches to the linux arm kernel list on behalf of a
team of kernel engineers -- drivers that are developed internally
are typically squashed down to a single patch for initial submission
and review (which seems to be the desired way to handle these things),
but in some cases they're the work of multiple people.  Is there a
better solution than to have one of the authors as the Author: and
mentioning the other contributors in the patch description?

Brian

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2008-06-05  8:27 99% recognizing multiple authors for a patch? Brian Swetland

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).