From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: Kees Cook <keescook@chromium•org>,
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 commits in Linus' tree
Date: Wed, 24 Feb 2021 11:49:42 +1100 [thread overview]
Message-ID: <20210224114942.4b07cece@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wi1FEJfk9r4Jw90kU3aayXka4Y4HOWdgAtVQHRFTgpQ+A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]
Hi Linus,
On Tue, 23 Feb 2021 16:33:47 -0800 Linus Torvalds <torvalds@linux-foundation•org> wrote:
>
> On Tue, Feb 23, 2021 at 4:31 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > are missing a Signed-off-by from their committer.
>
> Gaah. Maybe I should do some pre-pull hook or something to notice this
> automatically (like you clearly do).
I have attached the scripts I run over things after fetching them, but
before merging them (so not a hook, sorry). check_commits runs
check_fixes - but just for my convenience.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: check_commits --]
[-- Type: application/x-shellscript, Size: 1611 bytes --]
[-- Attachment #1.3: check_fixes --]
[-- Type: application/x-shellscript, Size: 4299 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-24 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 0:31 linux-next: Signed-off-by missing for commits in Linus' tree Stephen Rothwell
2021-02-24 0:33 ` Linus Torvalds
2021-02-24 0:49 ` Stephen Rothwell [this message]
2021-02-24 20:27 ` Kees Cook
2021-02-24 21:30 ` Kees Cook
2021-02-27 23:38 ` Linus Walleij
2021-02-24 19:52 ` Kees Cook
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=20210224114942.4b07cece@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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