From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] docs: Fixing "sphinxify coccinelle.txt"?
Date: Fri, 7 Oct 2016 15:08:53 +0200 [thread overview]
Message-ID: <09f3f798-5b9b-df84-e864-0593ee74e0cc@users.sourceforge.net> (raw)
In-Reply-To: <b17b77b4-9604-59c0-7808-09463a6a83f5@users.sourceforge.net>
>>> 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
>>
>> How about submitting a patch to fix the problem?
>
> Is the published commit (from 2016-08-08 / 2016-08-18) generally questionable
> as I see it by the interface "cgit" at the moment?
>
> * Does this one contain only the deletion of the file "Documentation/coccinelle.txt"?
It seems that I got an inappropriate impression from this kind of
data display alone.
The display for the changed file name contains only the desired addition.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/dev-tools/coccinelle.rst?id=4b9033a33494ec9154d63e706e9e47f7eb3fd59e
> I find another data display also interesting and more promising.
> https://patchwork.kernel.org/patch/9269973/
>
> * Should this patch about the desired file format conversion become available
> also by the other known interfaces?
The interface "cgit v0.12" does not indicate the involved "renaming" (similarity index 56%)
so far which can be better seen in the downloadable patch file.
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: cocci@systeme.lip6.fr
Subject: Re: docs: Fixing "sphinxify coccinelle.txt"?
Date: Fri, 07 Oct 2016 13:08:53 +0000 [thread overview]
Message-ID: <09f3f798-5b9b-df84-e864-0593ee74e0cc@users.sourceforge.net> (raw)
In-Reply-To: <b17b77b4-9604-59c0-7808-09463a6a83f5@users.sourceforge.net>
>>> 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?idK9033a33494ec9154d63e706e9e47f7eb3fd59e
>>>
>>> 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È02e87fbe2d4dd58982d01b3c39bc5a781223aa#n4
>>
>> How about submitting a patch to fix the problem?
>
> Is the published commit (from 2016-08-08 / 2016-08-18) generally questionable
> as I see it by the interface "cgit" at the moment?
>
> * Does this one contain only the deletion of the file "Documentation/coccinelle.txt"?
It seems that I got an inappropriate impression from this kind of
data display alone.
The display for the changed file name contains only the desired addition.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/dev-tools/coccinelle.rst?idK9033a33494ec9154d63e706e9e47f7eb3fd59e
> I find another data display also interesting and more promising.
> https://patchwork.kernel.org/patch/9269973/
>
> * Should this patch about the desired file format conversion become available
> also by the other known interfaces?
The interface "cgit v0.12" does not indicate the involved "renaming" (similarity index 56%)
so far which can be better seen in the downloadable patch file.
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>, Jonathan Corbet <corbet@lwn.net>
Cc: Coccinelle <cocci@systeme.lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
"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, linux-doc@vger.kernel.org
Subject: Re: docs: Fixing "sphinxify coccinelle.txt"?
Date: Fri, 7 Oct 2016 15:08:53 +0200 [thread overview]
Message-ID: <09f3f798-5b9b-df84-e864-0593ee74e0cc@users.sourceforge.net> (raw)
In-Reply-To: <b17b77b4-9604-59c0-7808-09463a6a83f5@users.sourceforge.net>
>>> 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
>>
>> How about submitting a patch to fix the problem?
>
> Is the published commit (from 2016-08-08 / 2016-08-18) generally questionable
> as I see it by the interface "cgit" at the moment?
>
> * Does this one contain only the deletion of the file "Documentation/coccinelle.txt"?
It seems that I got an inappropriate impression from this kind of
data display alone.
The display for the changed file name contains only the desired addition.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/dev-tools/coccinelle.rst?id=4b9033a33494ec9154d63e706e9e47f7eb3fd59e
> I find another data display also interesting and more promising.
> https://patchwork.kernel.org/patch/9269973/
>
> * Should this patch about the desired file format conversion become available
> also by the other known interfaces?
The interface "cgit v0.12" does not indicate the involved "renaming" (similarity index 56%)
so far which can be better seen in the downloadable patch file.
Regards,
Markus
next prev parent reply other threads:[~2016-10-07 13:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 5:47 [Cocci] scripts/coccicheck: Update for a comment? SF Markus Elfring
2016-10-07 5:47 ` SF Markus Elfring
2016-10-07 5:47 ` SF Markus Elfring
2016-10-07 5:50 ` [Cocci] " Julia Lawall
2016-10-07 5:50 ` Julia Lawall
2016-10-07 5:50 ` Julia Lawall
2016-10-07 6:00 ` [Cocci] " SF Markus Elfring
2016-10-07 6:00 ` SF Markus Elfring
2016-10-07 6:00 ` SF Markus Elfring
2016-10-07 6:06 ` [Cocci] " Julia Lawall
2016-10-07 6:06 ` Julia Lawall
2016-10-07 6:06 ` Julia Lawall
2016-10-07 6:23 ` [Cocci] " SF Markus Elfring
2016-10-07 6:23 ` SF Markus Elfring
2016-10-07 6:23 ` SF Markus Elfring
2016-10-07 6:27 ` [Cocci] " Julia Lawall
2016-10-07 6:27 ` Julia Lawall
2016-10-07 6:27 ` Julia Lawall
2016-10-07 7:19 ` [Cocci] " SF Markus Elfring
2016-10-07 7:19 ` SF Markus Elfring
2016-10-07 7:19 ` SF Markus Elfring
2016-10-07 13:20 ` [Cocci] " SF Markus Elfring
2016-10-07 13:20 ` SF Markus Elfring
2016-10-07 13:20 ` SF Markus Elfring
2016-10-07 14:16 ` [Cocci] [PATCH] scripts/coccicheck: Update reference for the corresponding documentation SF Markus Elfring
2016-10-07 14:16 ` SF Markus Elfring
2016-10-07 14:16 ` SF Markus Elfring
2016-10-07 18:30 ` [Cocci] " Julia Lawall
2016-10-07 18:30 ` Julia Lawall
2016-10-07 18:30 ` Julia Lawall
2016-10-11 7:52 ` [Cocci] " Michal Marek
2016-10-11 7:52 ` Michal Marek
2016-10-11 7:52 ` Michal Marek
2016-10-07 12:22 ` [Cocci] docs: Fixing "sphinxify coccinelle.txt"? SF Markus Elfring
2016-10-07 12:22 ` SF Markus Elfring
2016-10-07 12:22 ` SF Markus Elfring
2016-10-07 13:08 ` SF Markus Elfring [this message]
2016-10-07 13:08 ` 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=09f3f798-5b9b-df84-e864-0593ee74e0cc@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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.