public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Nicolas Palix <nicolas.palix@imag.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Cocci] [PATCH 3/3] Coccinelle: Update the options used to the new option scheme
Date: Wed, 03 Jul 2013 16:04:33 +0200	[thread overview]
Message-ID: <51D42F71.9030701@suse.cz> (raw)
In-Reply-To: <CAAxaTiMgaCp17um0NnF2gbWDoRZnb2GOq-50LRAvV_dDdEsjRg@mail.gmail.com>

On 3.7.2013 15:52, Nicolas Palix wrote:
> Hi,
> 
> On Wed, Jul 3, 2013 at 3:36 PM, Michal Marek <mmarek@suse.cz> wrote:
>> On 20.6.2013 13:10, Nicolas Palix wrote:
>>> spatch has changed its option scheme.
>>> E.g., --no_show_diff is now --no-show-diff
>>>
>>> This patch updates:
>>>  - scripts/coccicheck
>>>  - Semantic patches under scripts/coccinelle/
>>
>> Will the new syntax work with older spatch versions?
>> I mean, it's
>> probably fair to require a recent version, but it should be documented IMO.
> 
> It is the opposite. The new spatch still supports the old
> naming scheme. The more conventional naming has been introduced
> in spatch version 1.0.0-rc11 in March 2012. I will send a new patch to
> document that point.

Thanks.


>> Also, there was no patch 2/3 in this series, only 1/3 and 3/3.
> 
> It seems you finally found the v2 of this one. :)

Yes :).

Michal


  reply	other threads:[~2013-07-03 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 11:10 [PATCH 1/3] Coccinelle: Update section of MAINTAINERS Nicolas Palix
2013-06-20 11:10 ` [PATCH 3/3] Coccinelle: Update the options used to the new option scheme Nicolas Palix
2013-07-03 13:36   ` Michal Marek
2013-07-03 13:52     ` [Cocci] " Nicolas Palix
2013-07-03 14:04       ` Michal Marek [this message]
2013-07-03 13:33 ` [PATCH 1/3] Coccinelle: Update section of MAINTAINERS Michal Marek

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=51D42F71.9030701@suse.cz \
    --to=mmarek@suse.cz \
    --cc=cocci@systeme.lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --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