From: Joe Perches <joe@perches.com>
To: Aditya <yashsri421@gmail.com>, linux-kernel@vger.kernel.org
Cc: lukas.bulwahn@gmail.com, daniel@iogearbox.net,
peterz@infradead.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH v6] checkpatch: add fix for non-standard signature - co-authored-by
Date: Sat, 05 Dec 2020 04:03:23 -0800 [thread overview]
Message-ID: <7b8289150f47b1fe32fc85f2082a4b727f2b1664.camel@perches.com> (raw)
In-Reply-To: <b9048b9c-22cb-fc47-8e87-1c091a9cc822@gmail.com>
On Sat, 2020-12-05 at 15:52 +0530, Aditya wrote:
> On 4/12/20 8:10 pm, Aditya Srivastava wrote:
> > Currently, checkpatch.pl warns us for BAD_SIGN_OFF on the usage of
> > non-standard signatures.
[]
> > The standard signature equivalent for 'Co-authored-by' is
> > 'Co-developed-by'.
> >
> > Provide a fix by suggesting users with this signature alternative and
> > replacing.
> we were planning to introduce a fix for
> suggesting users to use "Co-developed-by" tag over "Co-authored-by"
> and I noticed that you have earlier used "Co-authored-by" tag.
>
> We feel that users perhaps use this tag as they are unaware of its
> standard equivalent tag, "Co-developed-by"
As I do not particularly approve of this patch,
"we" does not include "me", nor is it I presume
the royal usage.
Please specify who the "we" is here.
next prev parent reply other threads:[~2020-12-05 13:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:29 [PATCH v5] checkpatch: add fix and improve warning msg for Non-standard signature Aditya Srivastava
2020-12-01 17:24 ` Joe Perches
2020-12-01 18:21 ` Lukas Bulwahn
2020-12-01 18:39 ` Joe Perches
2020-12-02 9:08 ` [PATCH] checkpatch: add fix for non-standard signature - co-authored-by Aditya Srivastava
2020-12-02 17:16 ` Joe Perches
2020-12-02 18:30 ` [PATCH -mmots] " Aditya Srivastava
2020-12-02 18:56 ` Joe Perches
2020-12-03 9:59 ` Aditya
2020-12-03 10:59 ` Lukas Bulwahn
2020-12-03 12:23 ` Aditya
2020-12-03 18:57 ` [Linux-kernel-mentees] " Greg KH
2020-12-03 19:00 ` Lukas Bulwahn
2020-12-03 19:25 ` Greg KH
2020-12-03 19:31 ` Joe Perches
2020-12-04 14:40 ` [PATCH v6] " Aditya Srivastava
2020-12-04 15:59 ` Joe Perches
2020-12-05 10:22 ` Aditya
2020-12-05 12:03 ` Joe Perches [this message]
2020-12-05 12:55 ` Aditya
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=7b8289150f47b1fe32fc85f2082a4b727f2b1664.camel@perches.com \
--to=joe@perches.com \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=peterz@infradead.org \
--cc=yashsri421@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®