cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Denis Efremov <yefremov.denis@gmail.com>
To: cocci@systeme.lip6.fr
Subject: Re: [Cocci] release of version 1.1.0
Date: Sat, 27 Feb 2021 12:03:22 +0300	[thread overview]
Message-ID: <47b8a2cd-ff8a-ac8c-a9b1-015488bbc959@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2102270905410.2926@hadrien>

Hi,

Great news!

Could you please create release tag on GitHub?
This will allow me to add this version to tests and add new opam package version.
Currently, I use these versions for tests:
https://github.com/evdenis/cvehound/blob/master/.github/workflows/test.yml#L25

BTW, is there 1.0.9 version? I see that fedora provides 1.0.9 version,
but there is not release tag for it and there is no opam package for it.

Thanks,
Denis

On 2/27/21 11:11 AM, Julia Lawall wrote:
> A new version 1.1.0 has been released.  The most interesting change is the
> ability to put spatch command line options in a .cocci file, for example:
> 
> #spatch --very-quiet -j 8 --recursive-includes --include-headers-for-types
> 
> Other specific improvements are an improved handling of attributes and a
> more efficient treatment of header files (all thanks to Jaskaran Singh).
> 
> Various other small issues have been addressed.
> 
> All of these changes have already been available on github.
> 
> julia
> _______________________________________________
> Cocci mailing list
> Cocci@systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
> 
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2021-02-27  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27  8:11 [Cocci] release of version 1.1.0 Julia Lawall
2021-02-27  9:03 ` Denis Efremov [this message]
2021-02-27  9:14   ` Julia Lawall
2021-02-27 14:38     ` Denis Efremov
2021-02-27 14:47       ` Julia Lawall
2021-02-28 20:01 ` [Cocci] Checking evolution according to " Markus Elfring
2021-03-02 11:43   ` Richard W.M. Jones

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=47b8a2cd-ff8a-ac8c-a9b1-015488bbc959@gmail.com \
    --to=yefremov.denis@gmail.com \
    --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).