From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Request for .sig files for xen 3.4.3
Date: Fri, 18 Jun 2010 13:46:36 +0200 [thread overview]
Message-ID: <4C1B5C9C.7030901@invisiblethingslab.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 538 bytes --]
Hi,
I noticed that there is not .sig file for xen 3.4.3 tarball at
bits.xensource.com (and probably for older versions too).
Can you add this file, just like you do now for xen4:
http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz.sig
I know that you sign the 3.4.3 release in hg repo, but having such a
handy .sig file on the fileserver for official tarballs would simplify
RPM packaging -- a script would be able to automatically download and
verify the needed xen-${VERSION}.tar.gz.
Thanks,
joanna.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2010-06-18 11:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C1B5C9C.7030901@invisiblethingslab.com \
--to=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).