From: Joe Perches <joe@perches.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] checkpatch: add new warnings to author signoff checks.
Date: Mon, 05 Oct 2020 01:05:49 -0700 [thread overview]
Message-ID: <c51588b4e8a2096c1453070b983da5ce8617a622.camel@perches.com> (raw)
In-Reply-To: <CABJPP5BwVmWiFcxHKdCYnN_mOE1G=eHUDq8yqqHFaO3cYhp+oA@mail.gmail.com>
On Mon, 2020-10-05 at 13:10 +0530, Dwaipayan Ray wrote:
> On Mon, Oct 5, 2020 at 12:48 PM Joe Perches <joe@perches.com> wrote:
> > On Mon, 2020-10-05 at 12:18 +0530, Dwaipayan Ray wrote:
> > > The author signed-off-by checks are currently very vague.
> > > Cases like same name or same address are not handled separately.
[]
> > And for mismatches, it's really not known that
> > it should be one way or the or the other is it?
> >
>
> I think that's true. But since the mail in the
> From: part is the one which with others are being
> compared, I think maybe it should have the higher
> priority, and be treated as the expected one.
I rather expect it to be the other way around.
The Signed-off-by: line should be authoritative
as that is what is put in the commit log.
next prev parent reply other threads:[~2020-10-05 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 6:48 Dwaipayan Ray
2020-10-05 7:18 ` Joe Perches
2020-10-05 7:40 ` Dwaipayan Ray
2020-10-05 8:05 ` Joe Perches [this message]
[not found] ` <CABJPP5CAY+qJU8wnGZ7JgugeN9CyFbdct6nAsxpY0NdyaNuWLQ@mail.gmail.com>
[not found] ` <f1536dd1c1fbf53a848b27a2817a973fbf809719.camel@perches.com>
2020-10-05 8:52 ` Dwaipayan Ray
2020-10-05 7:30 ` Lukas Bulwahn
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=c51588b4e8a2096c1453070b983da5ce8617a622.camel@perches.com \
--to=joe@perches.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@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®