From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.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 12:27:02 -0800 [thread overview]
Message-ID: <202102241225.11226B262@keescook> (raw)
In-Reply-To: <20210224114942.4b07cece@canb.auug.org.au>
On Wed, Feb 24, 2021 at 11:49:42AM +1100, Stephen Rothwell wrote:
> 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.
Thank you! I've added these to my PR workflow now, and it yells quite loudly.
I'm still looking at some kind of push hook too...
--
Kees Cook
next prev parent reply other threads:[~2021-02-24 20:27 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
2021-02-24 20:27 ` Kees Cook [this message]
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=202102241225.11226B262@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.