From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
seabios@seabios.org, Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [SeaBIOS] [SEABIOS] Plans for either 1.9.1 or 1.10.0?
Date: Thu, 14 Jan 2016 18:14:45 +0100 [thread overview]
Message-ID: <5697D785.7010608@redhat.com> (raw)
In-Reply-To: <1452789411.19513.58.camel@redhat.com>
On 01/14/16 17:36, Gerd Hoffmann wrote:
> On Do, 2016-01-14 at 14:50 +0000, Ian Campbell wrote:
>> Hello,
>>
>> The xen.git development branch currently points to SeaBIOS rel-1.9.0, but
>> Roger has tripped over a build issue which is fixed by 3b8c5378dfe2 "build:
>> fix typo in buildversion.py".
>>
>> Is there any plan for either a 1.9.1 or a 1.10.0 in the near future which
>> would include this, so I can roll forward to that?
>
> 1.10 will take a while ...
>
>> Or if not a 1.9.1 release perhaps for now just a 1.9-stable branch could be
>> created?
>
> 1.9-stable created now, with the patch above cherry-picked.
>
> Doing 1.9.1 soonish (next week maybe) is fine with me. If someone would
> like to see other patches backported to 1.9-stable please speak up now.
It's been suggested (by you :)) that
76327b9f32a009245c215f4a3c5d58a01b5310ae be cherry-picked into 1.9.1 as
well, perhaps.
Just raising it here, should you have forgotten. Also copying Marcel.
Thanks
Laszlo
next prev parent reply other threads:[~2016-01-14 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 14:50 [SEABIOS] Plans for either 1.9.1 or 1.10.0? Ian Campbell
2016-01-14 16:36 ` [SeaBIOS] " Gerd Hoffmann
[not found] ` <1452789411.19513.58.camel@redhat.com>
2016-01-14 16:41 ` Ian Campbell
2016-01-14 17:14 ` Laszlo Ersek [this message]
2016-01-15 10:00 ` Gerd Hoffmann
2016-02-15 8:40 ` Gerd Hoffmann
[not found] ` <1455525648.7504.1.camel@redhat.com>
2016-02-16 13:37 ` 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=5697D785.7010608@redhat.com \
--to=lersek@redhat.com \
--cc=ian.campbell@citrix.com \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=seabios@seabios.org \
--cc=xen-devel@lists.xen.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.