From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] New release after 1.0.7?
Date: Mon, 10 Sep 2018 12:43:44 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1809101241150.3655@hadrien> (raw)
In-Reply-To: <1536564277.3224.7.camel@sipsolutions.net>
On Mon, 10 Sep 2018, Johannes Berg wrote:
> Julia,
>
> On Tue, 2018-08-14 at 15:19 +0200, Julia Lawall wrote:
>
> > Sorry, I'm not sure where 1.0.7 came from. [...]
>
> > I would indeed like to make a release now that the compiations issues are
> > resolved and things seem more stable.
>
> Were you able to clear this up?
>
> I see now that the website advertises the 1.0.7 release, however
>
> * it's not tagged in git(hub) - all previous releases have a tag
> * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
> the website
> * it *looks* like the actual 1.0.7 release was cut from a much newer
> git commit, likely with the fix?
I'm still somewhat lost about it. There is now a 1.0.7 source code on the
web site, which is the proper 1.0.7. But the binaries on the web site are
still 1.0.6. The previous thing that seemed to be 1.0.7 was an accidental
side effect of a test of the release script. I think that my engineer was
waiting me to confirm something before putting a tag in github, but I'm
not sure what I was to confirm. I will try to clear everything up. But
the source code on the Coccinelle website is the official 1.0.7.
julia
next prev parent reply other threads:[~2018-09-10 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 13:09 [Cocci] New release after 1.0.7? Luciano Coelho
2018-08-14 13:19 ` Julia Lawall
2018-08-14 13:32 ` 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-15 8:55 ` [Cocci] Adjustment for const qualification SF Markus Elfring
2018-08-15 9:28 ` Julia Lawall
2018-08-15 9:36 ` SF Markus Elfring
2018-08-15 9:40 ` Julia Lawall
2018-09-10 7:24 ` [Cocci] New release after 1.0.7? Johannes Berg
2018-09-10 10:43 ` Julia Lawall [this message]
2018-09-12 10:14 ` Julia Lawall
2018-09-12 10:16 ` 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=alpine.DEB.2.20.1809101241150.3655@hadrien \
--to=julia.lawall@lip6.fr \
--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).