All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@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: Thu, 22 Oct 2015 17:02:59 +0100	[thread overview]
Message-ID: <20151022160258.GM5060@zion.uk.xensource.com> (raw)
In-Reply-To: <22057.1980.705627.525934@mariner.uk.xensource.com>

On Thu, Oct 22, 2015 at 04:58:52PM +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH] Config.mk: update OVMF changeset"):
> > On Wed, 2015-10-14 at 12:41 +0100, Wei Liu wrote:
> > > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> > 
> > Acked + applied.
> > 
> > Ian, I beleive Stefano would like to see this in 4.6 at some point.
> ...
> > To ssh://xenbits.xen.org/home/xen/git/ovmf.git
> >    cb9a7eb..af9785a  af9785a9ed61daea52b47f0bf448f1f228beee1e -> master
> 
> This pulls in 782 commits.  That's hardly desirable for a stable
> release, surely ?  Does OVMF not have a stable branch ?
> 

No, upstream doesn't have stable branch. And we don't have our own
stable branch at the moment due to upstream doesn't make release or
maintain stable branch.

Currently the only method to see upstream changes ended in our stable
branch is to make backport request like this.

Wei.

> Ian.

  reply	other threads:[~2015-10-22 16:03 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 [this message]
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
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=20151022160258.GM5060@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.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.