From: Julia Lawall <julia.lawall@lip6.fr>
To: Luciano Coelho <luciano.coelho@intel.com>
Cc: cocci@systeme.lip6.fr, backports@vger.kernel.org
Subject: Re: [Cocci] New release after 1.0.7?
Date: Tue, 14 Aug 2018 15:19:55 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1808141515280.3371@hadrien> (raw)
In-Reply-To: <32b52167e7dd5734ba4aa5f21aa1fddd257e6292.camel@intel.com>
On Tue, 14 Aug 2018, Luciano Coelho wrote:
> Hi,
>
> Is there a plan for a new release after 1.0.7? 1.0.7 was not tagged and
> no tarballs were released, so I'm not sure what is the status of it.
> Additionally, I've had problems compiling it, and bisected it to this
> commit:
>
> commit 7ab8f01b63d7cdec988e5f05065f3c18fdab7319 (refs/bisect/bad)
> Author: Thierry Martinez <thierry.martinez@inria.fr>
> AuthorDate: Wed Jun 20 15:46:18 2018 +0200
> Commit: Thierry Martinez <thierry.martinez@inria.fr>
> CommitDate: Wed Jun 20 15:46:18 2018 +0200
>
> Allow bytecode compilation for pyml/generate
>
> This change generalizes a patch submitted by
> Christopher Zimmermann <chrisz@openbsd.org>
> for allowing pyml/generate to be compiled by ocamlc if ocamlopt
> is not available.
>
> The rules are adapted from pyml-current/Makefile.
>
> Nevertheless, the compilation problem I had seems to be fixed in the
> latest master (commit 97695d059cd5).
>
> We (in the Linux backports project) have made a change to support the
> new attributes style[1], which was supposed to work with 1.0.6, but
> that seems to be broken too.
>
> We don't want to revert to using the pre-1.0.6 versions, so we are
> waiting for new release to choose for our project. So, my question
> again, can we expect a new stable release any time soon?
Sorry, I'm not sure where 1.0.7 came from. I think that the compilation
issues should not be resolved, although if someone still sees problems
with the github version please report them. I'm surprised that the
attributes have degraded, since I don't recall a change with respect to
that recently. Could you send a .c and .cocci file that shows the
problem?
I would indeed like to make a release now that the compiations issues are
resolved and things seem more stable.
julia
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/commit/?id=98272f479c2126a135dfcb12484e93d5888164ab
>
> --
> Cheers,
> Luca.
> _______________________________________________
> Cocci mailing list
> Cocci@systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-08-14 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 13:09 New release after 1.0.7? Luciano Coelho
2018-08-14 13:19 ` Julia Lawall [this message]
2018-08-14 13:32 ` [Cocci] " Luciano Coelho
2018-08-14 13:43 ` Julia Lawall
2018-08-14 14:39 ` Luciano Coelho
2018-08-16 7:05 ` Johannes Berg
2018-08-16 7:09 ` Luciano Coelho
[not found] ` <b417bf64-7970-8482-0246-ab00129b4657@users.sourceforge.net>
[not found] ` <alpine.DEB.2.20.1808151127520.2309@hadrien>
2018-08-16 5:45 ` [Cocci] Adjustment for const qualification SF Markus Elfring
2018-09-10 7:24 ` [Cocci] New release after 1.0.7? Johannes Berg
2018-09-10 10:43 ` Julia Lawall
2018-09-12 10:14 ` Julia Lawall
2018-09-12 10:16 ` Johannes Berg
2018-10-22 11:44 ` Arend van Spriel
2018-10-22 11:45 ` Johannes Berg
2018-10-22 19:49 ` Hauke Mehrtens
2018-10-22 20:46 ` Arend van Spriel
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=alpine.DEB.2.20.1808141515280.3371@hadrien \
--to=julia.lawall@lip6.fr \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=luciano.coelho@intel.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 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).