From: Piotr Hosowicz <piotr@hosowicz.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
John Hawley <warthog19@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 3.0.7 now on kernel.org
Date: Sun, 23 Oct 2011 14:24:53 +0200 [thread overview]
Message-ID: <4EA40795.3070603@example.com> (raw)
In-Reply-To: <20111023083131.GA13802@kroah.com>
On 23.10.2011 10:31, Greg KH wrote:
> You will note that the files are signed with my new kernel release
> signing key, and that the .tar file is signed, and then compressed, so
> there is not signatures for the individual compressed files.
And why is that? It's less handy.
--
- Jaka jest największa anomalia fizjologiczno-polityczna?
- Członek wysunięty z ramienia na czoło.
NP: Caligula's Horse - Equally Flawed
NB: 3.1.0-rc3
next prev parent reply other threads:[~2011-10-23 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 8:31 Linux 3.0.7 now on kernel.org Greg KH
2011-10-23 12:24 ` Piotr Hosowicz [this message]
2011-10-23 12:29 ` Greg KH
2011-10-23 13:22 ` H. Peter Anvin
2011-10-23 14:18 ` Frank Ch. Eigler
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=4EA40795.3070603@example.com \
--to=piotr@hosowicz.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=warthog19@gmail.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 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).