From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Extending source code at file end with SmPL
Date: Tue, 2 Feb 2016 13:23:28 +0100 [thread overview]
Message-ID: <56B09FC0.2090305@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1602021237150.2494@hadrien>
>> 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.
I am looking for possibilities to keep a tool like "spatch" the central
interface for the specification of desired source code changes.
I would like to avoid the patch generation for special search patterns
by various workarounds.
How many software development efforts are needed then to keep corresponding
context information (like line numbers for patch hunks) consistent?
Regards,
Markus
prev parent reply other threads:[~2016-02-02 12:23 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
2016-02-02 12:23 ` SF Markus Elfring [this message]
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=56B09FC0.2090305@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.