From: Julia Lawall <julia.lawall@lip6.fr>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Coccinelle <cocci@systeme.lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Jonathan Corbet <corbet@lwn.net>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Michal Marek <mmarek@suse.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: scripts/coccicheck: Update for a comment?
Date: Fri, 7 Oct 2016 08:27:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1610070824490.3074@hadrien> (raw)
In-Reply-To: <8d36952c-1dbb-bb26-ee57-3e1540c042c0@users.sourceforge.net>
On Fri, 7 Oct 2016, SF Markus Elfring wrote:
> >>>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4
> >>>
> >>> How about submitting a patch to fix the problem?
> >>
> >> I would appreciate to become a bit more sure about the current storage location
> >> which should be referenced in this file.
> >
> > In the Documentation directory find . -name "*cocci*"
> >
> > gives
> >
> > ./dev-tools/coccinelle.rst
> >
> > I think you could have done that yourself.
>
> Does the usage of the format "reStructuredText" trigger further considerations
> like the following?
>
> * Does your feedback suggest that the path from this source file should be put
> in related places?
>
> * Would it make sense to store such a file name in a special variable?
>
> * When would you refer to generated file formats (like PDF) for this use case?
Either you send the patch, or I will send the patch, when I have time,
with no credit to you. I'm not an expert on all of the future plans for
the documentation, The only think I know is where the file is now, and
that the file is perfectly readable in its rst format, and thus it seems
quite all right to reference it. If the situation change in the future,
we can have another patch in the future.
julia
next prev parent reply other threads:[~2016-10-07 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 5:47 SF Markus Elfring
2016-10-07 5:50 ` 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 [this message]
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=alpine.DEB.2.10.1610070824490.3074@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=elfring@users.sourceforge.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
all inboxes | Powered by JetHome®