From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Hesse <list@eworm.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 4.20.8
Date: Thu, 14 Feb 2019 16:49:59 +0100 [thread overview]
Message-ID: <20190214154959.GC9910@kroah.com> (raw)
In-Reply-To: <20190214155335.6112f334@leda>
On Thu, Feb 14, 2019 at 03:53:35PM +0100, Christian Hesse wrote:
> Greg KH <gregkh@linuxfoundation.org> on Tue, 2019/02/12 21:18:
> > I'm announcing the release of the 4.20.8 kernel.
>
> Versions 4.20.7 and 4.20.8 are missing signatures in git notes. Can you
> please add (or push) them? Thanks!
The tarballs would not have been created if the git note was not there.
So are you sure it isn't present?
Hm, odd, it doesn't look like it is, wow, I really messed this one up...
Ok, both notes now regenerated. That's what I get for trying to do 4
releases at the same time :(
greg k-h
next prev parent reply other threads:[~2019-02-14 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 20:18 Linux 4.20.8 Greg KH
2019-02-12 20:18 ` Greg KH
2019-02-14 14:53 ` Christian Hesse
2019-02-14 15:49 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-12 20:13 Greg KH
2019-02-12 20:18 ` Greg KH
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=20190214154959.GC9910@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list@eworm.de \
--cc=stable@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).