qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [qemu-web RFC PATCH] _download/source.html: show the GPG fingerprint for releases
Date: Mon, 8 Mar 2021 14:44:10 +0100	[thread overview]
Message-ID: <764b8f00-d582-45da-d18a-a130be0fc427@redhat.com> (raw)
In-Reply-To: <20210308111649.14898-1-alex.bennee@linaro.org>

On 08/03/21 12:16, Alex Bennée wrote:
> +          managers key, fingerprint:
> +          <pre><code>CEAC C9E1 5534 EBAB B82D  3FA0 3353 C9CE F108 B584</code></pre>.
> +          Alternatively stay on the bleeding edge with the
> +	  <a href="https://gitlab.com/qemu-project/qemu">git repository!</a></p>
>   	<h2>Build instructions</h2>
>   
>   	{% for release in site.data.releases offset: 0 limit: 1 %}
>   	<p>To download and build QEMU {{release.branch}}.{{release.patch}}:</p>
>   <pre>wgethttps://download.qemu.org/qemu-{{release.branch}}.{{release.patch}}.tar.xz
> +# optional verify signature
> +wget https://download.qemu.org/qemu-{{release.branch}}.{{release.patch}}.tar.xz.sig
> +gpg --output qemu-{{release.branch}}.{{release.patch}}.tar.xz --verify qemu-{{release.branch}}.{{release.patch}}.tar.xz.sig
> +# extract and build

Maybe add some <b> to either the comments or the commands?

(For reference, the result is visible at 
https://bonzini.gitlab.io/qemu-web/download/#source).

Paolo



  reply	other threads:[~2021-03-08 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 11:16 [qemu-web RFC PATCH] _download/source.html: show the GPG fingerprint for releases Alex Bennée
2021-03-08 13:44 ` Paolo Bonzini [this message]
2021-03-08 13:57 ` Thomas Huth
2021-03-08 14:03 ` Peter Maydell

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=764b8f00-d582-45da-d18a-a130be0fc427@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).