{"thread":{"id":"13808","subject":"recognizing multiple authors for a patch?","startedAt":"2008-06-05T08:27:08Z","lastAt":"2008-06-05T08:27:08Z","messageCount":1,"participants":["Brian Swetland"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"78721","messageId":"20080605082708.GA28166@bulgaria.corp.google.com","threadId":"13808","inReplyTo":null,"subject":"recognizing multiple authors for a patch?","fromName":"Brian Swetland","fromEmail":"swetland@google.com","sentAt":"2008-06-05T08:27:08Z","receivedAt":"2008-06-05T08:27:08Z","isPatch":false,"sender":{"key":"swetland@google.com","avatar":"https://gravatar.com/avatar/b26b7c772097c55d8febb0fc027dd2ef577a05994a321819f49ab3c9153ac8b1?d=mp&s=160"},"body":"\nNicolas Pitre said, in the thread on the \"preserve the committer\" patch:\n> I think this is against the purpose of the committer field to preserve\n> it from a commit that was not made by you.  What really really has to be\n> preserved is the author field of course.  But attributing commit action\n> to someone else than yourself when you are the one reorganizing commits\n> is misrepresentation.\n\nWhich reminds me of a longstanding question I have -- how best to\nrepresent patches which have multiple authors?\n\nI'm submitted patches to the linux arm kernel list on behalf of a\nteam of kernel engineers -- drivers that are developed internally\nare typically squashed down to a single patch for initial submission\nand review (which seems to be the desired way to handle these things),\nbut in some cases they're the work of multiple people.  Is there a\nbetter solution than to have one of the authors as the Author: and\nmentioning the other contributors in the patch description?\n\nBrian\n"}]}