From: Krzysztof Kozlowski <krzk@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: workflows@vger.kernel.org
Subject: Re: script to check "Fixes:" tags
Date: Fri, 27 Sep 2019 09:08:25 +0200 [thread overview]
Message-ID: <20190927070825.GA18955@pi3> (raw)
In-Reply-To: <20190926195143.GA1742392@kroah.com>
On Thu, Sep 26, 2019 at 09:51:43PM +0200, Greg KH wrote:
> Since this list was created to share scripts, here's one that I
> currently use to test that the "Fixes:" tags are correct on a commit. I
> run it on all patches that I accept into my trees, after getting emails
> from Stephen one too many times :)
>
> It's almost entirely based on Stephen's original script, but has been
> changed a bit in formatting and usage to be a stand-alone script that
> anyone can use.
>
> To use:
> verify_fixes.sh GIT_RANGE
>
> if all is good, script will print nothing out and exit with success. If
> there is a problem it will be printed out and the script will exit with
> an error that you can check from any other program.
>
> It it 'shellcheck' clean, but I'm sure that there are other things wrong
> with it, so feel free to point out problems.
>
> And should stuff like this be in the kernel tree itself?
+1
Also a kernel.org repo for maintainer scripts would be useful. Extending
own scripts for generic usage it's a lot of boring and not needed (for
the owner) task. But if someone else does the job...
Best regards,
Krzysztof
next prev parent reply other threads:[~2019-09-27 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 19:51 script to check "Fixes:" tags Greg KH
2019-09-27 7:08 ` Krzysztof Kozlowski [this message]
2019-09-27 7:49 ` Geert Uytterhoeven
2019-09-27 12:01 ` Rob Herring
2019-09-27 18:03 ` Greg KH
2019-09-27 18:01 ` Greg KH
2019-09-27 18:06 ` Geert Uytterhoeven
2019-09-27 18:35 ` Greg KH
2019-09-27 19:00 ` Geert Uytterhoeven
2019-09-27 19:46 ` Theodore Y. Ts'o
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=20190927070825.GA18955@pi3 \
--to=krzk@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=workflows@vger.kernel.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 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).