linux-kernel - Re: process? [Re: Crypto Fixes for 4.19]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180919170055.GB32582@1wt.eu>
Date:   Wed, 19 Sep 2018 19:00:55 +0200
From:   Willy Tarreau <w@....eu>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "David S. Miller" <davem@...emloft.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: process? [Re: Crypto Fixes for 4.19]

On Wed, Sep 19, 2018 at 09:48:42AM -0700, Randy Dunlap wrote:
> On 9/19/18 9:40 AM, Greg KH wrote:
> > On Wed, Sep 19, 2018 at 09:10:55AM -0700, Randy Dunlap wrote:
> >> submitting-patches.rst says:
> >> The Signed-off-by: tag indicates that the signer was involved in the
> >> development of the patch, or that he/she was in the patch's delivery path.
> > 
> > Yes, but not for git pulls.
> > 
> > I have not applied any patches sent in emails at this point in time, so
> > there's nothing that I could have even signed off on.
> 
> OK, I see.

Just FWIW, if this line was added, it would change the commit message
hence the resulting hash. That's why it only appears on patches really
committed by the mentioned people (typically using "git am").

Willy