From: Markus Elfring <Markus.Elfring@web.de>
To: Peter Foley <pefoley2@pefoley.com>,
cocci@inria.fr, Julia Lawall <Julia.Lawall@inria.fr>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: [cocci] [PATCH] scripts: coccicheck: Avoid warning about spurious escape
Date: Thu, 26 Jan 2023 16:38:30 +0100 [thread overview]
Message-ID: <11ec2c22-4df1-8056-f490-7367d06a949c@web.de> (raw)
In-Reply-To: <20230113-cocci-v1-1-0f4ae50494d3@pefoley.com>
> +++ b/scripts/coccicheck
…
> +$SPATCH --help | grep -e "--jobs" > /dev/null && USE_JOBS="yes"
How do you think about to use single quotes instead of double quotes?
Regards,
Markus
next prev parent reply other threads:[~2023-01-26 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 17:29 [cocci] [PATCH] scripts: coccicheck: Avoid warning about spurious escape Peter Foley
2023-01-26 15:38 ` Markus Elfring [this message]
2023-02-25 19:27 ` 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=11ec2c22-4df1-8056-f490-7367d06a949c@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=pefoley2@pefoley.com \
/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).