From: Anthony PERARD <anthony.perard@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
<xen-devel@lists.xenproject.org>
Subject: Re: [XEN PATCH] Config.mk: update OVMF to edk2-stable202108
Date: Tue, 31 Aug 2021 14:48:43 +0100 [thread overview]
Message-ID: <YS4zO5P4TcUBLDe7@perard> (raw)
In-Reply-To: <b19def29-7287-0aa8-6bf6-1ca022de1355@suse.com>
On Tue, Aug 31, 2021 at 03:01:54PM +0200, Jan Beulich wrote:
> On 31.08.2021 14:36, Anthony PERARD wrote:
> > Update to the latest stable tag.
>
> Largely out of curiosity - if that's truly a tag, ...
Well, it's a git tag, but it's not signed by upstream :-(.
Upstream started to do a release for OVMF every 3 months somewhat
recently. They will stop taking new feature and only take fixes for a
couple of weeks, then tag the tree.
> > --- a/Config.mk
> > +++ b/Config.mk
> > @@ -244,7 +244,7 @@ QEMU_TRADITIONAL_URL ?= git://xenbits.xen.org/qemu-xen-traditional.git
> > SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
> > MINIOS_UPSTREAM_URL ?= git://xenbits.xen.org/mini-os.git
> > endif
> > -OVMF_UPSTREAM_REVISION ?= b37cfdd2807181aed2fee1e17bd7ec1190db266a
> > +OVMF_UPSTREAM_REVISION ?= 7b4a99be8a39c12d3a7fc4b8db9f0eab4ac688d5
>
> ... why not refer to it here and instead spell out a hash?
Since the tag isn't signed, it's probably better to keep using a hash.
--
Anthony PERARD
next prev parent reply other threads:[~2021-08-31 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 12:36 [XEN PATCH] Config.mk: update OVMF to edk2-stable202108 Anthony PERARD
2021-08-31 13:01 ` Jan Beulich
2021-08-31 13:48 ` Anthony PERARD [this message]
2021-08-31 13:58 ` Ian Jackson
2021-09-28 7:17 ` Anthony PERARD
2021-09-28 11:51 ` Ian Jackson
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=YS4zO5P4TcUBLDe7@perard \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.