Re: linux-next: Signed-off-by missing for commit in the xfs tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Dave,

On Tue, 4 Oct 2022 09:21:03 +1100 Dave Chinner <david@xxxxxxxxxxxxx> 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: pgptBWzGY33KF.pgp
Description: OpenPGP digital signature


[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux