All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
	George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] Update QEMU_UPSTREAM_REVISION
Date: Tue, 28 Jan 2014 11:17:26 -0500	[thread overview]
Message-ID: <20140128161726.GB6094@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401281607070.4373@kaball.uk.xensource.com>

On Tue, Jan 28, 2014 at 04:09:13PM +0000, Stefano Stabellini wrote:
> On Tue, 28 Jan 2014, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jan 28, 2014 at 03:23:19PM +0000, Stefano Stabellini wrote:
> > > Switch back to master.
> > 
> > Could you say why please?
> 
> See this thread: http://marc.info/?l=xen-devel&m=139090192108528

Just read it after I sent this email out :-)

I was thinking that the commit message should have at least
some description. Like 'Because we are going for rc2 and
its time to test new code' or 'rc1 tag had bugs, rc2 does
not.'


> 
> This should just be an automatic commit (that at the moment
> unfortunately is manual) to switch the xen build system to clone the
> master branch of qemu-xen instead of the RC1 tag.
> Obviously we switch to cloning the RC1 tag for the RC1 release. However
> now that RC1 is over we should go back to master.

Or for the pre-rc2 tag.

> 
> > > Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > > 
> > > diff --git a/Config.mk b/Config.mk
> > > index 55dce20..484cfdb 100644
> > > --- a/Config.mk
> > > +++ b/Config.mk
> > > @@ -234,7 +234,7 @@ QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
> > >  SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
> > >  endif
> > >  OVMF_UPSTREAM_REVISION ?= 447d264115c476142f884af0be287622cd244423
> > > -QEMU_UPSTREAM_REVISION ?= qemu-xen-4.4.0-rc1
> > > +QEMU_UPSTREAM_REVISION ?= master
> > >  SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
> > >  # Fri Aug 2 14:12:09 2013 -0400
> > >  # Fix bug in CBFS file walking with compressed files.
> > > 
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xen.org
> > > http://lists.xen.org/xen-devel
> > 

  reply	other threads:[~2014-01-28 16:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 15:23 [PATCH] Update QEMU_UPSTREAM_REVISION Stefano Stabellini
2014-01-28 15:26 ` George Dunlap
2014-01-28 16:05 ` Konrad Rzeszutek Wilk
2014-01-28 16:09   ` Stefano Stabellini
2014-01-28 16:17     ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-19 16:34 Ian Jackson
2013-11-27 17:02 Anthony PERARD
2013-11-27 17:17 ` Ian Jackson
2013-11-27 17:31   ` Ian Campbell
2013-11-28 19:44     ` Anthony PERARD
2013-11-29 10:52       ` Ian Campbell
2013-12-02 11:30         ` George Dunlap
2013-12-02 11:40           ` Ian Campbell
2013-12-02 12:34           ` Ian Jackson
2013-12-04 14:53             ` 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=20140128161726.GB6094@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.