From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Coccinelle <cocci@systeme.lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Jonathan Corbet <corbet@lwn.net>,
Julia Lawall <Julia.Lawall@lip6.fr>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Michal Marek <mmarek@suse.com>,
Nicolas Palix <nicolas.palix@imag.fr>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: scripts/coccicheck: Update for a comment?
Date: Fri, 7 Oct 2016 07:47:20 +0200 [thread overview]
Message-ID: <ea62a1ea-c566-65a0-e2fd-2ee96839cf48@users.sourceforge.net> (raw)
Hello,
Information from a commit like "docs: sphinxify coccinelle.txt and add it
to dev-tools" caught also my software development attention.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/coccinelle.txt?id=4b9033a33494ec9154d63e706e9e47f7eb3fd59e
Did an other information from a comment become outdated in the script "coccicheck"
because of such changes for the documentation format?
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4
Regards,
Markus
next reply other threads:[~2016-10-07 5:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 5:47 SF Markus Elfring [this message]
2016-10-07 5:50 ` scripts/coccicheck: Update for a comment? Julia Lawall
2016-10-07 6:00 ` SF Markus Elfring
2016-10-07 6:06 ` Julia Lawall
2016-10-07 6:23 ` SF Markus Elfring
2016-10-07 6:27 ` Julia Lawall
2016-10-07 7:19 ` SF Markus Elfring
2016-10-07 13:20 ` SF Markus Elfring
2016-10-07 14:16 ` [PATCH] scripts/coccicheck: Update reference for the corresponding documentation SF Markus Elfring
2016-10-07 18:30 ` Julia Lawall
2016-10-11 7:52 ` Michal Marek
2016-10-07 12:22 ` docs: Fixing "sphinxify coccinelle.txt"? SF Markus Elfring
2016-10-07 13:08 ` SF Markus Elfring
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=ea62a1ea-c566-65a0-e2fd-2ee96839cf48@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.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