From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [Cocci] New release after 1.0.7?
Date: Mon, 22 Oct 2018 13:45:24 +0200 [thread overview]
Message-ID: <1be0fb185e04dd80f57fcf1fe04ddf5491601f3d.camel@sipsolutions.net> (raw)
In-Reply-To: <cf992997-868d-56dc-bd1e-1d2064af4def@broadcom.com> (sfid-20181022_134441_691066_8C44DEE7)
On Mon, 2018-10-22 at 13:44 +0200, Arend van Spriel wrote:
> On 9/12/2018 12:16 PM, Johannes Berg wrote:
> > On Wed, 2018-09-12 at 12:14 +0200, Julia Lawall wrote:
> >
> > > > 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?
> > >
> > > There is now a tag for the official release of 1.0.7 in github.
> >
> > Great, thanks!
>
> Were you able to build this tag? I probably have dependency issues on
> our build server. I tried following the install.txt in coccinelle repo,
> but still getting failures. Some hints might be useful. The server runs
> ubuntu trusty which is pretty old of course.
Hmm. I built something, either that tag or the tarball?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-10-22 11:45 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 ` [Cocci] " 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-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 [this message]
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=1be0fb185e04dd80f57fcf1fe04ddf5491601f3d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
/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).