From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
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: Tue, 4 Oct 2022 22:50:12 +1100 [thread overview]
Message-ID: <20221004225012.501e11ed@canb.auug.org.au> (raw)
In-Reply-To: <20221003222103.GM3600936@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Hi Dave,
On Tue, 4 Oct 2022 09:21:03 +1100 Dave Chinner <david@fromorbit.com> wrote:
>
> The commit matches exactly what was sent to the list. It's just
> that the patch was sent from a personal email address with a
> corporate signoff.
>
> Since when has that been an issue? I -personally- have been doing
> this for well over a decade and I'm pretty sure there are lots of
> other people who also do this.
If you are happy (as the maintainer), then fine. My script just could
not connect those 2 email addresses. I check for matches between the
address itself (the part between the <>) or a match between the "name"
part (before the <>). If either matches (or it is obvious) then I
don't report it.
I have reported very few of these.
> Hence if this is wrong, then we've got a tooling problem with b4.
> Why does b4 allow this rather than warn/fail if it's not actually
> allowed in the linux-next tree?
These reports are more of "is this right/was this a slipup?" rather
than "this is not allowed" i.e.. there are circumstances under which
the actual author does not (or cannot) provide a Signed-off-by and that
is OK.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-04 11:51 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 [this message]
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
-- 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=20221004225012.501e11ed@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=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).