From: paulmck@linux.ibm.com (Paul E. McKenney)
To: cocci@systeme.lip6.fr
Subject: [Cocci] sending out trewide patches
Date: Sat, 27 Oct 2018 10:14:38 -0700 [thread overview]
Message-ID: <20181027171438.GD4170@linux.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1810270831160.3588@hadrien>
On Sat, Oct 27, 2018 at 08:38:02AM +0200, Julia Lawall wrote:
> Hello,
>
> At OSS Europe, I got some questions about how to send out large
> Coccinelle-generated patches. Coccinelle provides a tool tools/splitpatch
> (go to the tools subdirectory of the Coccinelle distribution and run make)
> that splits patches by set of maintainers (the default), by directory
> (--dirmerge option), or by file (--nomerge option). There is a file
> tools/splitpatch.README that explains the various ways that it can be
> used, but the simplest is to create a patch normally using
> git format-patch -s, obtaining eg 0001-changes.patch, and then run
>
> splitpatch 0001-changes.patch
>
> The output will include a 0001-changes.cover file, a set of
> 0001-changesN.patch files with the various split patches, and a
> 0001-changes.cmd file for sending it off with git send-email.
>
> This is available in the latest github version of Coccinelle. Comments
> are welcome.
Thank you, Julia! I will give it a try.
Thanx, Paul
PS. And in case you didn't make it there... ;-)
https://www.spatchchicken.co.uk/
https://www.spatchchicken.co.uk/about-us.html
next prev parent reply other threads:[~2018-10-27 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 6:38 [Cocci] sending out trewide patches Julia Lawall
2018-10-27 17:14 ` Paul E. McKenney [this message]
2018-10-27 18:08 ` Julia Lawall
2018-10-30 19:45 ` Paul E. McKenney
2018-10-30 19:56 ` Julia Lawall
2018-10-30 20:04 ` Paul E. McKenney
2018-10-30 20:09 ` Julia Lawall
2018-10-30 20:35 ` Paul E. McKenney
2018-10-30 20:54 ` Paul E. McKenney
2018-10-30 21:11 ` Julia Lawall
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=20181027171438.GD4170@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=cocci@systeme.lip6.fr \
/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).