From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] scripts/coccicheck: Update for a comment?
Date: Fri, 7 Oct 2016 09:19:28 +0200 [thread overview]
Message-ID: <1e8a03cb-2ae0-c8e3-7910-97ad05903709@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1610070824490.3074@hadrien>
> Either you send the patch, or I will send the patch, when I have time,
> with no credit to you.
I am curious when "the time" will be appropriate.
> I'm not an expert on all of the future plans for the documentation,
I assumed that you know a bit more about the corresponding software evolution
than me.
> 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.
I can agree to such an information in principle.
> If the situation change in the future, we can have another patch
> in the future.
I would appreciate another clarification:
Do I overlook any commit for the discussed source file anyhow?
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/dev-tools/coccinelle.rst
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: scripts/coccicheck: Update for a comment?
Date: Fri, 07 Oct 2016 07:19:28 +0000 [thread overview]
Message-ID: <1e8a03cb-2ae0-c8e3-7910-97ad05903709@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1610070824490.3074@hadrien>
> Either you send the patch, or I will send the patch, when I have time,
> with no credit to you.
I am curious when "the time" will be appropriate.
> I'm not an expert on all of the future plans for the documentation,
I assumed that you know a bit more about the corresponding software evolution
than me.
> 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.
I can agree to such an information in principle.
> If the situation change in the future, we can have another patch
> in the future.
I would appreciate another clarification:
Do I overlook any commit for the discussed source file anyhow?
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/dev-tools/coccinelle.rst
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: 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 09:19:28 +0200 [thread overview]
Message-ID: <1e8a03cb-2ae0-c8e3-7910-97ad05903709@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1610070824490.3074@hadrien>
> Either you send the patch, or I will send the patch, when I have time,
> with no credit to you.
I am curious when "the time" will be appropriate.
> I'm not an expert on all of the future plans for the documentation,
I assumed that you know a bit more about the corresponding software evolution
than me.
> 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.
I can agree to such an information in principle.
> If the situation change in the future, we can have another patch
> in the future.
I would appreciate another clarification:
Do I overlook any commit for the discussed source file anyhow?
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/dev-tools/coccinelle.rst
Regards,
Markus
next prev parent reply other threads:[~2016-10-07 7:19 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 ` SF Markus Elfring [this message]
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 ` [Cocci] " SF Markus Elfring
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=1e8a03cb-2ae0-c8e3-7910-97ad05903709@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.