From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pvops0 git tree signing?
Date: Tue, 8 Jun 2010 09:37:19 -0400 [thread overview]
Message-ID: <20100608133719.GC4775@phenom.dumpdata.com> (raw)
In-Reply-To: <4C0E2EE7.8000305@invisiblethingslab.com>
On Tue, Jun 08, 2010 at 01:52:07PM +0200, Joanna Rutkowska wrote:
> So, any plans to start signing the pvops kernel commits? I'm really
> reluctant to build and sign, and then distribute, an RPM with the
> sources fetched from this repo, if I cannot verify they are authentic in
> any way. I can easily imagine packagers from other distributions would
> think similar.
>
> It's really just a matter of signing Jeremy's key with the "Xen.org
> master key" (0x79BAD9D8), and then typing git tag -s after every major
> commit, no?
I don't know whether we are truly at a release stage yet? (there are
still tons of bugs). Or were you thinking more in terms of whenever
Jeremy merges Greg KH's stable 2.6.32 and then tag it?
next prev parent reply other threads:[~2010-06-08 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 11:52 pvops0 git tree signing? Joanna Rutkowska
2010-06-08 13:37 ` Konrad Rzeszutek Wilk [this message]
2010-06-08 13:43 ` Joanna Rutkowska
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=20100608133719.GC4775@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=joanna@invisiblethingslab.com \
--cc=xen-devel@lists.xensource.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).