All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad
Date: Thu, 30 Jul 2015 15:46:45 +0100	[thread overview]
Message-ID: <1438267605.11600.363.camel@citrix.com> (raw)
In-Reply-To: <21946.13738.269462.357206@mariner.uk.xensource.com>

On Thu, 2015-07-30 at 15:33 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[RFC for-4.7] Switching to a single qemu tree each 
> per qemu-xen and qemu-trad"):
> ...
> > qemu-xen-traditional:
> ...
> >     XXX why do staging/* exist, and what pushes from staging to the 
> > other?
> >     Should we ditch one or the other?
> 
> Once upon a time, some of these had their own push gate.  They are
> nowadays always pushed together.  The staging branches should be
> abolished.

Thanks, I suspect as much.

> > The main open question is what to do about the existing split repos for
> > existing stable branches. We could:
> > 
> >       * Teach osstest (ap-push) to push to the old tree as well as the 
> > new
> >         for existing (<= 4.6) branches only.
> >       * Push a Config.mk update to every stable branch and retire the
> >         existing trees on the next relevant point release, if there is 
> > one.
> 
> We could do both of these, so we have a transitional period.

That could work, yes.

e.g. perhaps do the dual push until the corresponding point release
happens?

  reply	other threads:[~2015-07-30 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 14:22 [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad Ian Campbell
2015-07-30 14:33 ` Ian Jackson
2015-07-30 14:46   ` Ian Campbell [this message]
2015-07-30 14:40 ` Andrew Cooper
2015-07-30 15:11   ` Ian Jackson
2015-07-30 14:51 ` Vitaly Kuznetsov
2015-07-30 14:57   ` Ian Campbell
2015-08-03 10:14   ` George Dunlap
2015-08-11 14:45 ` Jan Beulich

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=1438267605.11600.363.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --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.