From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Extending source code at file end with SmPL
Date: Tue, 2 Feb 2016 12:37:43 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1602021237150.2494@hadrien> (raw)
In-Reply-To: <56B09453.5080501@users.sourceforge.net>
On Tue, 2 Feb 2016, SF Markus Elfring wrote:
> >> Would it make sense to clarify any further extensions?
> >
> > Why don't you just use cat?
>
> A software tool like "cat" does usually not generate the desired patch file.
>
> I would also appreciate if the input file will be checked according to specific
> source code search patterns.
I guess you can generate what you want with Coccinelle, and then cat it
onto the end of some other file and do diff to get a patch.
julia
>
> Regards,
> Markus
>
next prev parent reply other threads:[~2016-02-02 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 9:55 [Cocci] Extending source code at file end with SmPL SF Markus Elfring
[not found] ` <alpine.DEB.2.10.1602021111510.2494@hadrien>
2016-02-02 10:56 ` SF Markus Elfring
[not found] ` <alpine.DEB.2.10.1602021205280.2494@hadrien>
2016-02-02 11:34 ` SF Markus Elfring
2016-02-02 11:37 ` Julia Lawall [this message]
2016-02-02 12:23 ` SF Markus Elfring
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=alpine.DEB.2.10.1602021237150.2494@hadrien \
--to=julia.lawall@lip6.fr \
--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