linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-xfs@vger.kernel.org, Stephen Zhang <starzhangzsd@gmail.com>,
	Shida Zhang <zhangshida@kylinos.cn>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the xfs tree
Date: Wed, 5 Oct 2022 12:46:42 -0400	[thread overview]
Message-ID: <20221005164642.qhzyfmsekgqrerhd@meerkat.local> (raw)
In-Reply-To: <20221004210400.GO3600936@dread.disaster.area>

On Wed, Oct 05, 2022 at 08:04:00AM +1100, Dave Chinner wrote:
> > That said... I think we should get in the habit of asking patch authors
> > to make sure that at least one of the email or name strings match
> > between the From and SOB tags.  I can see how people who grok even less
> > about how Chinese names work than I do (read: lawyers) might get fussy
> > about this kind of thing.
> 
> As per above, the normal solution is an explicit "From: <foo>" line
> that matches the SOB.  It's just annoying that our new-fangled tools
> haven't encoded this long-standing convention to warn us when we
> pull a patch with a from-tag that doesn't match a sob-tag.

This is the case of "there's multiple opinions of what's right" here. The
logic for matching "person tags" is as follows:

- check that entire email matches (a.smith@intel.com == a.smith@intel.com)
- failing that, check that the name is a full match 
  ("Alex Smith" == "Alex Smith")
- failing that, check if there's a comma in the From and swap it around
  ("Smith, Alex" == "Alex Smith")

The last two checks were added based on a request, I'm pretty sure. Before
that we only did full email check and complained about trailer mismatches if
it was failing. If the previous behaviour was "more right" then I'm happy to
roll back or put this up for a "what is more correct" vote.

-K

  parent reply	other threads:[~2022-10-05 16:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 20:23 linux-next: Signed-off-by missing for commit in the xfs tree Stephen Rothwell
2022-10-03 22:21 ` Dave Chinner
2022-10-04 11:50   ` Stephen Rothwell
2022-10-04 15:57     ` Darrick J. Wong
2022-10-04 21:04       ` Dave Chinner
2022-10-05  2:52         ` Stephen Zhang
2022-10-05  3:01           ` Darrick J. Wong
2022-10-05  3:13             ` Willy Tarreau
2022-10-05 16:46         ` Konstantin Ryabitsev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-06 22:26 Stephen Rothwell
2020-07-26 21:57 Stephen Rothwell
2018-06-04 22:03 Stephen Rothwell
2018-06-04 22:17 ` Darrick J. Wong
2017-08-16 21:48 Stephen Rothwell

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=20221005164642.qhzyfmsekgqrerhd@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=starzhangzsd@gmail.com \
    --cc=zhangshida@kylinos.cn \
    /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;
as well as URLs for NNTP newsgroup(s).