From: Benoit Taine <benoit.taine@lip6.fr>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: kernelnewbies@kernelnewbies.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
Date: Fri, 18 Jul 2014 16:46:21 +0200 [thread overview]
Message-ID: <20140718144621.GA12871@lip6.fr> (raw)
In-Reply-To: <CANZNk81LiTM9vY0dRV=T0BCT9k-BxU45Ojw_PyOcpdmtXHKM2Q@mail.gmail.com>
On 18/07/2014 17:38, Andrey Utkin wrote:
> Is there script for automated checkpatch.pl && get_maintainers.pl &&
> git send-email for range of commits? I see none. Would it be welcome
> to submit such one to kernel tree?
You can use `splitpatch` to split a patch into multiple mails with the
correct mailing list and maintainers. It generates a script to
chain-send these emails using `cocci-send-email` (a modified version of
`git-send-email`).
Both are available in the `tools/` directory of coccinelle's
distribution <http://coccinelle.lip6.fr/>.
--
Benoît Taine
Master cycle intern
Regal Team. LIP6
next prev parent reply other threads:[~2014-07-18 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 14:38 How to automate checkpatch && get_maintainers && git send-email of commits range? Andrey Utkin
2014-07-18 14:46 ` Benoit Taine [this message]
2014-07-18 15:24 ` Andrey Utkin
2014-07-18 20:40 ` Greg KH
2014-07-18 22:22 ` Theodore Ts'o
2014-07-18 22:47 ` Joe Perches
2014-07-18 22:50 ` Joe Perches
2014-07-19 1:31 ` Steven Rostedt
2014-07-19 3:35 ` Hillf Danton
2014-07-19 4:05 ` Nick Krause
2014-07-20 22:23 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2014-07-18 14:55 Alexey Dobriyan
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=20140718144621.GA12871@lip6.fr \
--to=benoit.taine@lip6.fr \
--cc=andrey.krieger.utkin@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@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