From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: SeaBIOS update on master?
Date: Wed, 11 Feb 2015 10:56:44 +0000 [thread overview]
Message-ID: <1423652204.27551.16.camel@citrix.com> (raw)
In-Reply-To: <54DB2304020000780005EE08@mail.emea.novell.com>
On Wed, 2015-02-11 at 08:38 +0000, Jan Beulich wrote:
> Ian,
>
> I notice there is 1.7.5.2 available upstream - are there plans for us
> to update, or are we going to wait for 1.7.6 or 1.8 or whatever is
> going to be next? (I ask without having checked whether there are
> any fixes that would specifically concern us.)
Thanks for the reminder.
Normally want to track their releases during the dev cycle (when I
remember) but a new release is imminent, so I think rather than bumping
twice I may as well wait for it (whatever version it ends up being).
I haven't looked for specific fixes either.
Ian.
next prev parent reply other threads:[~2015-02-11 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 8:38 SeaBIOS update on master? Jan Beulich
2015-02-11 10:56 ` Ian Campbell [this message]
2015-02-19 8:43 ` Ian Campbell
2015-02-19 9:49 ` Wei Liu
2015-02-19 17:20 ` Ian Campbell
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=1423652204.27551.16.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@suse.com \
--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.