xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stephen Spector <stephen.spector@citrix.com>
Subject: Re: request to sign software
Date: Tue, 30 Mar 2010 10:59:37 +0100	[thread overview]
Message-ID: <C7D78A19.EF47%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BB1C889.3080204@invisiblethingslab.com>

On 30/03/2010 10:46, "Joanna Rutkowska" <joanna@invisiblethingslab.com>
wrote:

> Right. But I think it would make lots of sense for Jeremy to tag, at
> least some of the pvops branches (stable-2.6.{31.32}.x), anyway.
> Otherwise this every-changing repo might scare away lots of people.
> Perhaps Jeremy could apply some tag (and sign it) every week, or after
> some more major merges, etc.
> 
> Would be nice e.g. to have some particular commit from the pvops marked
> as the official release for the upcoming Xen 4.0.0, wouldn't it?

Indeed it would.

 K.

  reply	other threads:[~2010-03-30  9:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 10:02 request to sign software Joanna Rutkowska
2010-03-29 17:47 ` Jeremy Fitzhardinge
2010-03-29 21:09   ` Joanna Rutkowska
2010-03-30  7:00     ` Keir Fraser
2010-03-30  9:46       ` Joanna Rutkowska
2010-03-30  9:59         ` Keir Fraser [this message]
2010-04-01 16:37       ` Ian Jackson
2010-04-01 20:06         ` Weird RAM handling with Xen 3.4.3-RC3 Thomas Goirand
2010-03-30  9:58   ` request to sign software 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=C7D78A19.EF47%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=joanna@invisiblethingslab.com \
    --cc=stephen.spector@citrix.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).