From: mcgrof@kernel.org (Luis R. Rodriguez)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation
Date: Wed, 22 Jun 2016 02:07:30 +0200 [thread overview]
Message-ID: <20160622000730.GL25646@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1606212318280.2040@localhost6.localdomain6>
On Tue, Jun 21, 2016 at 11:18:41PM +0200, Julia Lawall wrote:
>
>
> On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote:
>
> > Hi,
> >
> > Le 21/06/16 ? 21:21, Luis R. Rodriguez a ?crit :
> > > Sprinkling *tons* of documentation on the script is not a good
> > > idea, instead refer to a wiki for further coccicheck documentation:
> > >
> > > https://bottest.wiki.kernel.org/coccicheck
> > >
> > > This page shall always refer to the linux-next iteration of
> > > scripts/coccicheck.
> >
> > Can you say a word about Documentation/coccinelle.txt too ?
> > And update it according to the script changes.
>
> I think this would be a good idea.
I'd much prefer to just keep docs in a wiki, and we nuke this outdated doc or
refer in the Documentation/coccinelle.txt to the wiki. This lets us document
things much faster and lets us add more information in a much nicer format. But
that's just me...
The existing file Documentation/coccinelle.txt even provides documentation on
how to build coccinelle --we're way passed that point. Note, I havne't
updated the docs on the wiki to refer to any of this, and would not unless
these changes get merged at least to linux-next.
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: "Nicolas Palix (LIG)" <Nicolas.Palix@imag.fr>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Gilles.Muller@lip6.fr, mmarek@suse.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
gregkh@linuxfoundation.org, markivx@codeaurora.org,
stephen.boyd@linaro.org, zohar@linux.vnet.ibm.com,
broonie@kernel.org, ming.lei@canonical.com, tiwai@suse.de,
johannes@sipsolutions.net, chunkeey@googlemail.com,
hauke@hauke-m.de, jwboyer@fedoraproject.org,
dmitry.torokhov@gmail.com, dwmw2@infradead.org, jslaby@suse.com,
torvalds@linux-foundation.org, deepa.kernel@gmail.com,
cocci@systeme.lip6.fr
Subject: Re: [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation
Date: Wed, 22 Jun 2016 02:07:30 +0200 [thread overview]
Message-ID: <20160622000730.GL25646@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1606212318280.2040@localhost6.localdomain6>
On Tue, Jun 21, 2016 at 11:18:41PM +0200, Julia Lawall wrote:
>
>
> On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote:
>
> > Hi,
> >
> > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit :
> > > Sprinkling *tons* of documentation on the script is not a good
> > > idea, instead refer to a wiki for further coccicheck documentation:
> > >
> > > https://bottest.wiki.kernel.org/coccicheck
> > >
> > > This page shall always refer to the linux-next iteration of
> > > scripts/coccicheck.
> >
> > Can you say a word about Documentation/coccinelle.txt too ?
> > And update it according to the script changes.
>
> I think this would be a good idea.
I'd much prefer to just keep docs in a wiki, and we nuke this outdated doc or
refer in the Documentation/coccinelle.txt to the wiki. This lets us document
things much faster and lets us add more information in a much nicer format. But
that's just me...
The existing file Documentation/coccinelle.txt even provides documentation on
how to build coccinelle --we're way passed that point. Note, I havne't
updated the docs on the wiki to refer to any of this, and would not unless
these changes get merged at least to linux-next.
Luis
next prev parent reply other threads:[~2016-06-22 0:07 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 19:21 [Cocci] [PATCH v3 0/8] coccicheck: modernize Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 19:21 ` [Cocci] [PATCH v3 1/8] coccicheck: move spatch binary check up Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 20:34 ` [Cocci] " Nicolas Palix (LIG)
2016-06-21 20:34 ` Nicolas Palix (LIG)
2016-06-21 19:21 ` [Cocci] [PATCH v3 2/8] coccicheck: make SPFLAGS more useful Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-22 20:39 ` [Cocci] " Nicolas Palix (LIG)
2016-06-22 20:39 ` Nicolas Palix (LIG)
2016-06-21 19:21 ` [Cocci] [PATCH v3 3/8] coccicheck: enable parmap support Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 20:17 ` [Cocci] " Julia Lawall
2016-06-21 20:17 ` Julia Lawall
2016-06-21 20:39 ` [Cocci] " Luis R. Rodriguez
2016-06-21 20:39 ` Luis R. Rodriguez
2016-06-21 20:43 ` [Cocci] " Julia Lawall
2016-06-21 20:43 ` Julia Lawall
2016-06-21 20:54 ` [Cocci] " Luis R. Rodriguez
2016-06-21 20:54 ` Luis R. Rodriguez
2016-06-21 21:10 ` [Cocci] " Julia Lawall
2016-06-21 21:10 ` Julia Lawall
2016-06-21 21:27 ` [Cocci] " Luis R. Rodriguez
2016-06-21 21:27 ` Luis R. Rodriguez
2016-06-21 21:31 ` [Cocci] " Julia Lawall
2016-06-21 21:31 ` Julia Lawall
2016-06-21 21:00 ` [Cocci] " Nicolas Palix (LIG)
2016-06-21 21:00 ` Nicolas Palix (LIG)
2016-06-21 21:28 ` [Cocci] " Luis R. Rodriguez
2016-06-21 21:28 ` Luis R. Rodriguez
2016-06-21 21:32 ` [Cocci] " Julia Lawall
2016-06-21 21:32 ` Julia Lawall
2016-06-21 21:39 ` [Cocci] " Luis R. Rodriguez
2016-06-21 21:39 ` Luis R. Rodriguez
2016-06-21 21:44 ` [Cocci] " Julia Lawall
2016-06-21 21:44 ` Julia Lawall
2016-06-21 22:14 ` [Cocci] " Luis R. Rodriguez
2016-06-21 22:14 ` Luis R. Rodriguez
2016-06-22 5:25 ` [Cocci] " Julia Lawall
2016-06-22 5:25 ` Julia Lawall
2016-06-22 15:10 ` [Cocci] " Luis R. Rodriguez
2016-06-22 15:10 ` Luis R. Rodriguez
2016-06-22 19:47 ` Julia Lawall
2016-06-22 19:47 ` Julia Lawall
2016-06-21 19:21 ` [Cocci] [PATCH v3 4/8] coccicheck: replace --very-quiet with --quit when debugging Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 19:21 ` [Cocci] [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 20:29 ` [Cocci] " Julia Lawall
2016-06-21 20:29 ` Julia Lawall
2016-06-21 23:43 ` [Cocci] " Luis R. Rodriguez
2016-06-21 23:43 ` Luis R. Rodriguez
2016-06-22 5:53 ` [Cocci] " Julia Lawall
2016-06-22 5:53 ` Julia Lawall
2016-06-21 21:07 ` [Cocci] " Nicolas Palix (LIG)
2016-06-21 21:07 ` Nicolas Palix (LIG)
2016-06-21 21:12 ` [Cocci] " Julia Lawall
2016-06-21 21:12 ` Julia Lawall
2016-06-21 23:38 ` [Cocci] " Luis R. Rodriguez
2016-06-21 23:38 ` Luis R. Rodriguez
2016-06-22 5:51 ` [Cocci] " Julia Lawall
2016-06-22 5:51 ` Julia Lawall
2016-06-21 19:21 ` [Cocci] [PATCH v3 6/8] coccicheck: add support for requring a coccinelle version Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 21:11 ` [Cocci] " Nicolas Palix (LIG)
2016-06-21 21:11 ` Nicolas Palix (LIG)
2016-06-21 19:21 ` [Cocci] [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 21:14 ` [Cocci] " Nicolas Palix (LIG)
2016-06-21 21:14 ` Nicolas Palix (LIG)
2016-06-21 21:18 ` [Cocci] " Julia Lawall
2016-06-21 21:18 ` Julia Lawall
2016-06-22 0:07 ` Luis R. Rodriguez [this message]
2016-06-22 0:07 ` Luis R. Rodriguez
2016-06-22 5:56 ` [Cocci] " Julia Lawall
2016-06-22 5:56 ` Julia Lawall
2016-06-21 19:21 ` [Cocci] [PATCH v3 8/8] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci Luis R. Rodriguez
2016-06-21 19:21 ` Luis R. Rodriguez
2016-06-21 20:36 ` [Cocci] " Julia Lawall
2016-06-21 20:36 ` Julia Lawall
2016-06-21 21:17 ` [Cocci] " Nicolas Palix (LIG)
2016-06-21 21:17 ` Nicolas Palix (LIG)
2016-06-21 20:13 ` [Cocci] [PATCH v3 0/8] coccicheck: modernize Julia Lawall
2016-06-21 20:13 ` Julia Lawall
2016-06-21 20:51 ` [Cocci] " Luis R. Rodriguez
2016-06-21 20:51 ` Luis R. Rodriguez
2016-06-21 21:02 ` Julia Lawall
2016-06-21 21:02 ` Julia Lawall
2016-06-21 21:21 ` Luis R. Rodriguez
2016-06-21 21:21 ` Luis R. Rodriguez
2016-06-21 21:30 ` Julia Lawall
2016-06-21 21:30 ` Julia Lawall
2016-06-21 21:34 ` Luis R. Rodriguez
2016-06-21 21:34 ` Luis R. Rodriguez
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=20160622000730.GL25646@wotan.suse.de \
--to=mcgrof@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.