From: johannes@sipsolutions.net (Johannes Berg)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Parse error with genl-const.cocci
Date: Sat, 02 Dec 2017 08:47:04 +0100 [thread overview]
Message-ID: <1512200824.26976.1.camel@sipsolutions.net> (raw)
In-Reply-To: <0a0862ea-f5ac-f172-064d-6d8531d4db2d@gmail.com> (sfid-20171202_004859_725268_37874B7C)
On Fri, 2017-12-01 at 15:48 -0800, Remington Furman wrote:
>
> Following up, running gentree.py again (without modifying the
> copy list) worked fine.
Good to hear :-)
Out of curiosity - how long did it take?
johannes
next prev parent reply other threads:[~2017-12-02 7:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <925f98d2-047f-785f-4162-21b53a77cd62@gmail.com>
2017-12-01 8:27 ` [Cocci] Parse error with genl-const.cocci Johannes Berg
2017-12-01 9:18 ` Julia Lawall
2017-12-01 9:29 ` Johannes Berg
2017-12-01 10:00 ` Julia Lawall
2017-12-12 15:19 ` Remington Furman
2017-12-14 15:16 ` Julia Lawall
2017-12-19 9:41 ` Johannes Berg
2018-06-25 20:33 ` Johannes Berg
2017-12-01 17:57 ` Remington Furman
2017-12-01 18:02 ` Johannes Berg
2017-12-01 18:09 ` Remington Furman
2017-12-01 23:48 ` Remington Furman
2017-12-02 7:47 ` Johannes Berg [this message]
2017-12-01 18:57 ` Julia Lawall
2017-12-01 19:39 ` Johannes Berg
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=1512200824.26976.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).