From: Jonathan Corbet <corbet@lwn.net>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
<linux-kernel@vger.kernel.org>,
Eugeniu Rosca <roscaeugeniu@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] checkpatch: whitelist Originally-by: signature
Date: Fri, 15 Nov 2019 09:29:43 -0700 [thread overview]
Message-ID: <20191115092943.7c79f81e@lwn.net> (raw)
In-Reply-To: <20191115154627.GA2187@lxhi-065.adit-jv.com>
On Fri, 15 Nov 2019 16:46:27 +0100
Eugeniu Rosca <erosca@de.adit-jv.com> wrote:
> On Fri, Nov 15, 2019 at 07:09:17AM -0800, Joe Perches wrote:
> > On Fri, 2019-11-15 at 16:02 +0100, Eugeniu Rosca wrote:
> > > Oftentimes [1], the contributor would like to honor or give credits [2]
> > > to somebody's original ideas in the submission/reviewing process. While
> > > "Co-developed-by:" and "Suggested-by:" (currently whitelisted) could be
> > > employed for this purpose, they are not ideal.
> >
> > You need to get the use of this accepted into Documentation/process
> > before adding it to checkpatch
>
> If the change [*] makes sense to you, I can submit an update to
> Documentation/process/submitting-patches.rst
So there appear to be 89 patches with Originally-by in the entire Git
history, which isn't a a lot; there are 3x as many Co-developed-by tags,
which still isn't a huge number. I do wonder if it's worth recognizing
yet another tag with a subtly different shade of meaning here? My own
opinion doesn't matter a lot, but I'd like to have a sense that there is
wider acceptance of this tag before adding it to the docs.
Thanks,
jon
next prev parent reply other threads:[~2019-11-15 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 15:02 Eugeniu Rosca
2019-11-15 15:09 ` Joe Perches
2019-11-15 15:46 ` Eugeniu Rosca
2019-11-15 16:29 ` Jonathan Corbet [this message]
2019-11-15 17:21 ` Eugeniu Rosca
2019-11-27 9:25 ` Geert Uytterhoeven
2019-11-27 11:25 ` Eugeniu Rosca
2019-11-15 21:32 ` Joe Perches
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=20191115092943.7c79f81e@lwn.net \
--to=corbet@lwn.net \
--cc=apw@canonical.com \
--cc=erosca@de.adit-jv.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roscaeugeniu@gmail.com \
--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 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®