From: Stephen Rothwell <sfr@rothwell.id.au>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org,
Allison Henderson <allison.henderson@oracle.com>,
Chandan Babu R <chandanrlinux@gmail.com>,
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 the xfs tree
Date: Tue, 22 Jun 2021 09:06:12 +1000 [thread overview]
Message-ID: <20210622090612.15c37586@elm.ozlabs.ibm.com> (raw)
In-Reply-To: <20210621215159.GE3619569@locust>
[-- Attachment #1.1: Type: text/plain, Size: 720 bytes --]
Hi Darrick,
On Mon, 21 Jun 2021 14:51:59 -0700 "Darrick J. Wong" <djwong@kernel.org> wrote:
>
> Um... do you know if there's a commit hook or something that all of us
> can add to spot-check all this stuff? I would really like to spend my
> worry beans on about algorithms and code design, not worrying about how
> many signature rules can be bent before LT starts refusing pull requests.
Attached are the scripts I run over each tree as I fetch them each day.
The check_commits script calls the check_fixes script.
So, I fetch a maintainer's branch into a local branch and then run
check_commits ^origin/master <old head>..<new head>
origin/master is Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: check_commits --]
[-- Type: application/x-shellscript, Size: 1694 bytes --]
[-- Attachment #1.3: check_fixes --]
[-- Type: application/x-shellscript, Size: 4440 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-21 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 22:26 linux-next: Signed-off-by missing for commits in the xfs tree Stephen Rothwell
2021-06-21 17:12 ` Darrick J. Wong
2021-06-21 21:27 ` Stephen Rothwell
2021-06-21 21:51 ` Darrick J. Wong
2021-06-21 22:10 ` Stephen Rothwell
2021-06-21 23:06 ` Stephen Rothwell [this message]
2021-06-21 21:54 ` Dave Chinner
2021-08-10 21:49 Stephen Rothwell
2021-08-11 19:21 ` Darrick J. Wong
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=20210622090612.15c37586@elm.ozlabs.ibm.com \
--to=sfr@rothwell.id.au \
--cc=allison.henderson@oracle.com \
--cc=chandanrlinux@gmail.com \
--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=sfr@canb.auug.org.au \
/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).