From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] Config.mk: update OVMF changeset
Date: Fri, 23 Oct 2015 12:38:41 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1510231233010.15801@kaball.uk.xensource.com> (raw)
In-Reply-To: <22058.6010.169770.684351@mariner.uk.xensource.com>
On Fri, 23 Oct 2015, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [PATCH] Config.mk: update OVMF changeset"):
> > On Fri, 23 Oct 2015, Ian Campbell wrote:
> > > Yes. Those (that?) and the reasons why we aren't just trivially taking them
> > > are explained in the referenced thread.
>
> That explanation isn't very convincing to me.
>
> > I cannot believe we are going to move forward without a way to introduce
> > any OVMF fixes into the stable branches.
>
> It is fine to introduce OVMF fixes into stable branches, of course.
>
> But it is not fine to introduce other upstream changes to OVMF,
> willy-nilly.
>
> Obviously these two requirements cannot be satisfied without there
> being some branch of OVMF which contains the intended fixes, without
> the unwanted upstream development.
>
> If OVMF upstream do not have such a branch, we need to create one.
That's fine. We need the new branch in osstest and somebody maintaining
it.
next prev parent reply other threads:[~2015-10-23 11:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 11:41 [PATCH] Config.mk: update OVMF changeset Wei Liu
2015-10-22 15:55 ` Ian Campbell
2015-10-22 15:58 ` Ian Jackson
2015-10-22 16:02 ` Wei Liu
2015-10-22 16:09 ` Ian Campbell
2015-10-22 16:11 ` Stefano Stabellini
2015-10-22 17:08 ` Ian Jackson
2015-10-23 8:01 ` Jan Beulich
2015-10-23 9:11 ` Ian Campbell
2015-10-23 10:08 ` Stefano Stabellini
2015-10-23 11:18 ` Ian Jackson
2015-10-23 11:38 ` Stefano Stabellini [this message]
2015-10-23 11:56 ` Ian Jackson
2015-10-23 11:52 ` Jan Beulich
2015-10-23 12:16 ` Ian Campbell
2015-10-23 12:43 ` Stefano Stabellini
2015-10-23 12:56 ` Ian Campbell
2015-10-23 13:16 ` Fabio Fantoni
2015-10-23 13:38 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2020-08-12 9:55 Wei Liu
2018-07-25 14:38 Anthony PERARD
2017-09-22 17:20 Anthony PERARD
2017-09-25 7:31 ` Jan Beulich
2017-09-25 14:20 ` Dario Faggioli
2017-03-23 17:10 Anthony PERARD
2015-11-12 10:06 Wei Liu
2015-11-16 12:08 ` Ian Campbell
2015-11-16 12:10 ` Wei Liu
2013-12-08 20:50 Wei Liu
2013-12-09 11:04 ` George Dunlap
2013-12-09 11:10 ` Wei Liu
2013-12-09 11:17 ` George Dunlap
2013-12-09 11:33 ` Ian Campbell
2013-12-09 15:46 ` 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=alpine.DEB.2.02.1510231233010.15801@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.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.