From: Sumera Priyadarsini <sylphrenadin@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [PATCH 0/2] Add "use-patchdiff" option
Date: Fri, 2 Jul 2021 00:12:08 +0530 [thread overview]
Message-ID: <CACAkLup9dzuPDxNqtyirq5K38oDAfS=VQu=5brSJvVfv-a_mZA@mail.gmail.com> (raw)
In-Reply-To: <a205b3d2-5da2-8ed5-26a9-2103bee9a534@web.de>
On Wed, May 26, 2021 at 10:13 PM Markus Elfring <Markus.Elfring@web.de> wrote:
>
> > This patchset adds a feature to enable Coccinelle
> > to only check all those files in a directory which were
> > modified. It parses all the files obtained from the
> > output of "git diff" and checks them against the specified
> > cocci script.
> >
> > An example for passing the "use-patchdiff" option is:
>
> How do you think about to use the parameter name “use-files-from-diff”?
I would prefer something shorter, like "use-filesdiff" but I am okay
with either name as
long as the maintainers are okay with it. :)
Julia, what do you think? I will send a v2 with any of the above name options
(and/or any other changes that are suggested.)
Thanks,
Sumera
>
> Regards,
> Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2021-07-01 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 10:51 [Cocci] [PATCH 0/2] Add "use-patchdiff" option Sumera Priyadarsini
2021-05-26 10:52 ` [Cocci] [PATCH 1/2] parsing_cocci: Add feature to check only modified files Sumera Priyadarsini
2021-05-26 10:53 ` [Cocci] [PATCH 2/2] docs: manual: Add option description in spatch_options Sumera Priyadarsini
2021-05-26 16:43 ` [Cocci] [PATCH 0/2] Add "use-patchdiff" option Markus Elfring
2021-07-01 18:42 ` Sumera Priyadarsini [this message]
2021-07-01 18:50 ` 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='CACAkLup9dzuPDxNqtyirq5K38oDAfS=VQu=5brSJvVfv-a_mZA@mail.gmail.com' \
--to=sylphrenadin@gmail.com \
--cc=Markus.Elfring@web.de \
--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).