From: Markus Elfring <Markus.Elfring@web.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, cocci@inria.fr
Subject: Re: [cocci] Checking consequences from concatenation of SmPL rules
Date: Thu, 1 Sep 2022 20:12:29 +0200 [thread overview]
Message-ID: <568e61b3-03fd-6eeb-b723-c11205479765@web.de> (raw)
In-Reply-To: <220901.8635dbjfko.gmgdl@evledraar.gmail.com>
> Are there reasons for why this is a Bad Idea?
* Do you care for the uniqueness of SmPL rules?
* Special identifiers: initialize:python, finalize:python
* I recommend to handle operation modes for SmPL scripts in consistent ways.
* Would you like to reconsider risks for undesirable change mixtures?
* How do you think about previous feature requests?
Example:
2019-04-07
Support for SmPL rule groups
https://github.com/coccinelle/coccinelle/issues/164
Regards,
Markus
prev parent reply other threads:[~2022-09-01 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 15:00 [cocci] Optimizing *.cocci rules by concat'ing them Ævar Arnfjörð Bjarmason
2022-09-01 15:19 ` Julia Lawall
2022-09-01 18:12 ` 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=568e61b3-03fd-6eeb-b723-c11205479765@web.de \
--to=markus.elfring@web.de \
--cc=avarab@gmail.com \
--cc=cocci@inria.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).