All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Luciano Coelho <luciano.coelho@intel.com>,
	cocci@systeme.lip6.fr, backports@vger.kernel.org
Subject: Re: [Cocci] New release after 1.0.7?
Date: Wed, 12 Sep 2018 12:16:09 +0200	[thread overview]
Message-ID: <1536747369.3678.11.camel@sipsolutions.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1809121214160.31876@hadrien>

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!

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

WARNING: multiple messages have this Message-ID (diff)
From: johannes@sipsolutions.net (Johannes Berg)
To: cocci@systeme.lip6.fr
Subject: [Cocci] New release after 1.0.7?
Date: Wed, 12 Sep 2018 12:16:09 +0200	[thread overview]
Message-ID: <1536747369.3678.11.camel@sipsolutions.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1809121214160.31876@hadrien>

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!

johannes

  reply	other threads:[~2018-09-12 15:20 UTC|newest]

Thread overview: 30+ 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:09 ` [Cocci] " Luciano Coelho
2018-08-14 13:19 ` Julia Lawall
2018-08-14 13:19   ` Julia Lawall
2018-08-14 13:32   ` Luciano Coelho
2018-08-14 13:32     ` Luciano Coelho
2018-08-14 13:43     ` Julia Lawall
2018-08-14 13:43       ` Julia Lawall
2018-08-14 14:39       ` Luciano Coelho
2018-08-14 14:39         ` Luciano Coelho
2018-08-16  7:05         ` Johannes Berg
2018-08-16  7:05           ` Johannes Berg
2018-08-16  7:09           ` Luciano Coelho
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-08-16  5:45         ` SF Markus Elfring
2018-09-10  7:24   ` [Cocci] New release after 1.0.7? Johannes Berg
2018-09-10  7:24     ` Johannes Berg
2018-09-10 10:43     ` Julia Lawall
2018-09-10 10:43       ` Julia Lawall
2018-09-12 10:14     ` Julia Lawall
2018-09-12 10:14       ` Julia Lawall
2018-09-12 10:16       ` Johannes Berg [this message]
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=1536747369.3678.11.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.