mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>, Randy Dunlap <rdunlap@xenotime.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Subject: [RFC] Add a "Co-authored-by" commit tag
Date: Wed, 23 Jan 2013 15:48:02 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.1301231528020.26301@axis700.grange> (raw)

Hi all

In most cases we work on our patches from the beginning to the end, but 
from time to time it happens, that someone originates a patch but then 
becomes (temporarily) unable to continue with new reviews, so, someone 
picks it up from there and brings to a final form. Or simply even several 
persons work closely on one patch. A yet another case is, when someone 
posts a rough first version of a patch, but then someone else heavily 
reworks it and becomes the actual submitting author of the patch, still, 
the original author should be mentioned somehow too.

Currently we can do something like

From: Original Author <...>

Signed-off-by: Original Author <...>
[contributor-2@...: continued patch development since v2]
Signed-off-by: New Contributor <contributor-2@...>

But is this sufficient, wouldn't a "Co-authored-by" tag be a better match 
for similar situations?

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

                 reply	other threads:[~2013-01-23 14:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.64.1301231528020.26301@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=corbet@lwn.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sylvester.nawrocki@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

all inboxes | Powered by JetHome®