From: Michal Marek <mmarek@suse.cz>
To: Nicolas Palix <npalix.work@gmail.com>
Cc: Julia Lawall <julia@diku.dk>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <npalix@diku.dk>, Sam Ravnborg <sam@ravnborg.org>,
Joerg Roedel <joerg.roedel@amd.com>,
cocci@diku.dk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] Coccinelle: Improve user information with a new kind of comment
Date: Wed, 06 Oct 2010 14:52:51 +0200 [thread overview]
Message-ID: <4CAC7123.8090504@suse.cz> (raw)
In-Reply-To: <1286225141-22027-1-git-send-email-npalix.work@gmail.com>
On 4.10.2010 22:45, Nicolas Palix wrote:
> Improve user information with a new kind of comment
> about semantic patch output.
>
> Fix spelling.
>
> Signed-off-by: Nicolas Palix <npalix.work@gmail.com>
> Signed-off-by: Julia Lawall <julia@diku.dk>
> ---
> scripts/coccicheck | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index b8bcf1f..4655551 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -25,7 +25,7 @@ fi
>
> if [ "$MODE" = "" ] ; then
> if [ "$ONLINE" = "0" ] ; then
> - echo 'You have not explicitly specify the mode to use. Fallback to "report".'
> + echo 'You have not explicitly specified the mode to use. Fallback to "report".'
> echo 'You can specify the mode with "make coccicheck MODE=<mode>"'
> echo 'Available modes are: report, patch, context, org'
> fi
> @@ -52,7 +52,12 @@ coccinelle () {
>
> FILE=`echo $COCCI | sed "s|$srctree/||"`
>
> - echo "Processing `basename $COCCI` with option(s) \"$OPT\""
> + echo "Processing `basename $COCCI`"
> + echo "with option(s) \"$OPT\""
> + echo 'Semantic patch information:'
> +
> + sed -e '/\/\/#/!d' -e 's|^//#||' $COCCI
sed -ne 's|^//#||p' $COCCI :)
But I would put this after the "Message example to submit a patch".
free.cocci has the information in this order and it makes more sense
this way IMO (first general information, then details). And it would be
nice to only display the "Semantic patch information:" line if there
actually is some additional information in the semantic patch file.
Otherwise, the series looks OK to me.
> +
> echo 'Message example to submit a patch:'
>
> sed -e '/\/\/\//!d' -e 's|^///||' $COCCI
Michal
prev parent reply other threads:[~2010-10-06 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 20:45 [PATCH 2/5] Coccinelle: Improve user information with a new kind of comment Nicolas Palix
2010-10-06 12:52 ` Michal Marek [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=4CAC7123.8090504@suse.cz \
--to=mmarek@suse.cz \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=joerg.roedel@amd.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix.work@gmail.com \
--cc=npalix@diku.dk \
--cc=sam@ravnborg.org \
/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