mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] checkpatch: add new warnings to author signoff checks.
Date: Mon, 05 Oct 2020 14:09:45 -0700	[thread overview]
Message-ID: <c1ca28e77e8e3bfa7aadf3efa8ed70f97a9d369c.camel@perches.com> (raw)
In-Reply-To: <CABJPP5DDmurU9c2qCoJcg7hvwnkYo4LCx+TW6xKG2G23Uf_Cxw@mail.gmail.com>

On Tue, 2020-10-06 at 01:37 +0530, Dwaipayan Ray wrote:
> On Tue, Oct 6, 2020 at 1:07 AM Joe Perches <joe@perches.com> wrote:
> > On Tue, 2020-10-06 at 00:54 +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.
> > 
> > When you run tests for this, how many mismatches are
> > caused by name formatting changes like:
> > 
> > From: "Developer, J. Random" <jrd@bigcorp.com>
> > ...
> > Signed-off-by: "J. Random Developer" <jrd@bigcorp.com>?
> > 
> > Should these differences generate a warning?
> > 
> 
> Hi,
> I ran my tests on non merge commits between v5.7 and v5.8.
> 
> There were a total of 250 NO_AUTHOR_SIGN_OFF Warnings
> 
> 203 of these were email address mismatches.
> 32 of these were name mismatches.
> 
> So for the name mismatches, the typical cases are like:
> 
> 'From: tannerlove <tannerlove@google.com>' != 'Signed-off-by: Tanner
> Love <tannerlove@google.com>'
> 'From: "朱灿灿" <zhucancan@vivo.com>' != 'Signed-off-by: zhucancan
> <zhucancan@vivo.com>'
> 'From: Yuval Basson <ybason@marvell.com>' != 'Signed-off-by: Yuval
> Bason <ybason@marvell.com>'
> 'From: allen <allen.chen@ite.com.tw>' != 'Signed-off-by: Allen Chen
> <allen.chen@ite.com.tw>'
> 
> I didn't find the exact formatting change you mentioned in my commit range.
> But I did find something like:
> 
> 'From: "Paul A. Clarke" <pc@us.ibm.com>' != 'Signed-off-by: Paul
> Clarke <pc@us.ibm.com>'
> 
> So it's like some have parts of their names removed, some have language
> conflicts, and yet some have well different spellings, or initials,
> etc. It's like
> a wide variety of things happening here.
> 
> I think considering these, it should be warned about, and let people know
> that there might be something wrong going on.
> 
> What do you think?

Except for comments and quotes like:

	From: J. Random Developer (BigCorp) <jrd@bigcorp.com>
	Signed-off-by: "J. Random Developer" <jrd@bigcorp.com>

I think any time there's a mismatch, there
should be a warning emitted.

That includes any subaddress detail difference.



  reply	other threads:[~2020-10-05 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 19:24 Dwaipayan Ray
2020-10-05 19:37 ` Joe Perches
2020-10-05 20:07   ` Dwaipayan Ray
2020-10-05 21:09     ` Joe Perches [this message]
2020-10-06  4:23       ` Dwaipayan Ray
2020-10-06  4:38         ` Lukas Bulwahn
2020-10-06 13:15           ` Dwaipayan Ray
2020-10-06 18:28             ` 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=c1ca28e77e8e3bfa7aadf3efa8ed70f97a9d369c.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®