All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] checkpatch.pl investigation: NO_AUTHOR_SIGN_OFF issues
Date: Mon, 28 Sep 2020 17:09:52 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2009281706250.4154@felia> (raw)
In-Reply-To: <CABJPP5Dws9Q_5A0LeSWSTb-dgSQiguU5rOF-cEvDTTrfonfmEQ@mail.gmail.com>



On Mon, 28 Sep 2020, Dwaipayan Ray wrote:

> >
> > How about just starting a new thread instead?
> >
> > I will answer on the new thread.
> >
> > Lukas
> >
> 
> Sure, I will.
> 
> Also did my last mail go through to you?
>

Yes, that went through. I just did not have some immediate thought on any 
further response. I think it is a good idea but I had no strong feeling on 
louding rejecting or loudly raising acknowledgement to the idea.

Just go for it.

Lukas
 
> Quoted:
> > So I did run my script to evaluate the type of errors that were generated.
> > My results are from commits between v5.7 and v5.8
> >
> > 1) Same address, different name
> > There were 32 such instances. In general, there was no regularity in the
> > specific error.
> >
> > There were some cases with letter case mismatch. Like there was one
> > committer who used the names "Arend Van Spriel", and "Arend van Spriel".
> > I believe this error should not be generated and matching be made case
> > neutral.
> >
> > Apart from this, the rest of the cases in this category were some with missing
> > first or last names, using names in other languages or having commas in
> > one name, using initials etc. These should be warned about.
> >
> > 2) Same name, different address
> > There were 204 such instances. Most of them were of the form in which they
> > used a completely different email address.
> >
> > Only one case was found with an email extension.
> > <hpeter@gmail.com>
> > <hpeter+linux_kernel@gmail.com>
> > in commit 423d9118c624
> >
> > So in general I think most email mismatches should be specified by a WARN
> > and for email extension there should be a --strict CHECK.
> > What do you think of this?
> >
> > Thanks,
> > Dwaipayan.
> 
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2020-09-28 15:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 10:06 [Linux-kernel-mentees] checkpatch.pl investigation: NO_AUTHOR_SIGN_OFF issues Lukas Bulwahn
2020-09-18 10:29 ` Dwaipayan Ray
2020-09-18 10:44   ` Lukas Bulwahn
2020-09-21  9:07     ` Dwaipayan Ray
2020-09-21  9:12       ` Lukas Bulwahn
2020-09-21  9:15       ` Lukas Bulwahn
2020-09-22 13:21         ` Dwaipayan Ray
2020-09-22 18:38           ` Lukas Bulwahn
2020-09-22 19:08             ` Dwaipayan Ray
2020-09-23  7:32               ` Lukas Bulwahn
2020-09-23  7:38                 ` Dwaipayan Ray
2020-09-23  7:42                   ` Lukas Bulwahn
2020-09-25  4:18                     ` Dwaipayan Ray
2020-09-25  7:20                       ` Lukas Bulwahn
2020-09-25  7:29                         ` Dwaipayan Ray
2020-09-25  7:35                           ` Lukas Bulwahn
2020-09-26 11:31                             ` Dwaipayan Ray
2020-09-28 13:30                               ` Dwaipayan Ray
2020-09-28 14:09                                 ` Lukas Bulwahn
2020-09-28 14:20                                   ` Dwaipayan Ray
2020-09-28 15:09                                     ` Lukas Bulwahn [this message]
2020-09-28 15:06                               ` 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=alpine.DEB.2.21.2009281706250.4154@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    /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.