From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Fixing SmPL scripts for data output according to structured file formats
Date: Fri, 8 Nov 2019 14:05:20 +0100 [thread overview]
Message-ID: <9809f7a9-3a61-c926-2c81-eb31be07394a@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1911081350350.2465@hadrien>
> make coccicheck uses --no-show-diff at the approrpiate place so that the *
> have no effect if the context option is not chosen.
Thanks for your reminder on this command option.
How do you think about to look at possibilities around the redirection of output
to files so that diff hunks from matched source code fragments (according to
SmPL asterisk functionality) could be directly used from corresponding variables?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2019-11-08 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 12:15 [Cocci] Fixing SmPL scripts for data output according to structured file formats Markus Elfring
2019-11-08 12:51 ` Julia Lawall
2019-11-08 13:05 ` 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=9809f7a9-3a61-c926-2c81-eb31be07394a@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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).