[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d36952c-1dbb-bb26-ee57-3e1540c042c0@users.sourceforge.net>
Date: Fri, 7 Oct 2016 08:23:20 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Julia Lawall <julia.lawall@...6.fr>
Cc: Coccinelle <cocci@...teme.lip6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Jonathan Corbet <corbet@....net>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Michal Marek <mmarek@...e.com>,
Nicolas Palix <nicolas.palix@...g.fr>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: scripts/coccicheck: Update for a comment?
>>>> 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?
Regards,
Markus
Powered by blists - more mailing lists