All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/process: add Co-Developed-by: tag for patches with multiple authors
Date: Fri, 17 Nov 2017 15:46:33 -0700	[thread overview]
Message-ID: <20171117154633.59f657f9@lwn.net> (raw)
In-Reply-To: <20171116132309.GA8449@kroah.com>

On Thu, 16 Nov 2017 14:23:09 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:

> Sometimes a single patch is the result of multiple authors.  As git only
> can have one "author" of a patch, it is still good to properly give
> credit to the other developers of a commit.  To address this, document
> the "Co-Developed-by:" tag which can be used to show other authors of
> the patch.
> 
> Note, these other authors must also provide a Signed-off-by: tag as it
> is their work that is being submitted here.

So this seems good, and I'm seeing no objections.  I can go ahead and
apply it and ship it upward.

That said, I do think that there should maybe be a mention in
submitting-patches.rst as well, since we have a fair amount of discussion
of patch tags there.  *Someday* we'll have nice organized documentation
that doesn't scatter this stuff around, but that's not this day...

Thanks,

jon

  parent reply	other threads:[~2017-11-17 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 13:23 [PATCH] Documentation/process: add Co-Developed-by: tag for patches with multiple authors Greg Kroah-Hartman
2017-11-17 10:26 ` Thomas Gleixner
2017-11-17 10:37 ` Borislav Petkov
2017-11-17 22:46 ` Jonathan Corbet [this message]
2018-01-16 22:43 ` Kees Cook

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=20171117154633.59f657f9@lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.