From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
"cocci@systeme.lip6.fr" <cocci@systeme.lip6.fr>
Subject: Re: [PATCH] pycocci: sync pycocci with Coccinelle upstream
Date: Tue, 09 Jun 2015 08:29:33 +0200 [thread overview]
Message-ID: <1433831373.1892.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6W68eikvWE+YKKSUC3_S_pTLY-cJq5hGeRkKp2mx9dRMA@mail.gmail.com> (sfid-20150608_224340_079310_DA6B54D3)
On Mon, 2015-06-08 at 13:43 -0700, Luis R. Rodriguez wrote:
> On Mon, Jun 8, 2015 at 1:31 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Mon, 2015-06-08 at 13:01 -0700, Luis R. Rodriguez wrote:
> >> pycocci is now part of Coccinelle upstream. Coccinelle has a plan
> >> to actually extend multithreaded support to enable us to not have
> >> to script this out. Until then pyccoci is used and I'll sync both
> >> solutions up as there is a bit of latency between a coccinelle release
> >> and what we may need from pycocci.
> >
> > If it's upstream, do they ship it? If so it wouldn't be needed that we
> > have a copy, it seems?
>
> Indeed, Coccinelle 1.0 has pycocci except for this last patch I just
> mentioned. I think it is important enough for our sake that the errors
> are reported well, I think its fair to drop this in backports once
> Coccinelle 1.1 is released and we can reasonably expect users to have
> it installed.
Not sure I see the point in applying it now - clearly we haven't had any
issues here that required this change, so why bother?
johannes
WARNING: multiple messages have this Message-ID (diff)
From: johannes@sipsolutions.net (Johannes Berg)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH] pycocci: sync pycocci with Coccinelle upstream
Date: Tue, 09 Jun 2015 08:29:33 +0200 [thread overview]
Message-ID: <1433831373.1892.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6W68eikvWE+YKKSUC3_S_pTLY-cJq5hGeRkKp2mx9dRMA@mail.gmail.com> (sfid-20150608_224340_079310_DA6B54D3)
On Mon, 2015-06-08 at 13:43 -0700, Luis R. Rodriguez wrote:
> On Mon, Jun 8, 2015 at 1:31 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Mon, 2015-06-08 at 13:01 -0700, Luis R. Rodriguez wrote:
> >> pycocci is now part of Coccinelle upstream. Coccinelle has a plan
> >> to actually extend multithreaded support to enable us to not have
> >> to script this out. Until then pyccoci is used and I'll sync both
> >> solutions up as there is a bit of latency between a coccinelle release
> >> and what we may need from pycocci.
> >
> > If it's upstream, do they ship it? If so it wouldn't be needed that we
> > have a copy, it seems?
>
> Indeed, Coccinelle 1.0 has pycocci except for this last patch I just
> mentioned. I think it is important enough for our sake that the errors
> are reported well, I think its fair to drop this in backports once
> Coccinelle 1.1 is released and we can reasonably expect users to have
> it installed.
Not sure I see the point in applying it now - clearly we haven't had any
issues here that required this change, so why bother?
johannes
next prev parent reply other threads:[~2015-06-09 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 20:01 [PATCH] pycocci: sync pycocci with Coccinelle upstream Luis R. Rodriguez
2015-06-08 20:01 ` [Cocci] " Luis R. Rodriguez
2015-06-08 20:31 ` Johannes Berg
2015-06-08 20:31 ` [Cocci] " Johannes Berg
2015-06-08 20:43 ` Luis R. Rodriguez
2015-06-08 20:43 ` [Cocci] " Luis R. Rodriguez
2015-06-09 6:29 ` Johannes Berg [this message]
2015-06-09 6:29 ` Johannes Berg
2015-06-09 22:20 ` Luis R. Rodriguez
2015-06-09 22:20 ` [Cocci] " Luis R. Rodriguez
2015-06-09 22:22 ` Luis R. Rodriguez
2015-06-09 22:22 ` [Cocci] " Luis R. Rodriguez
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=1433831373.1892.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=mcgrof@do-not-panic.com \
/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.