All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: sfr@canb.auug.org.au, Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	david.vrabel@citrix.com, boris.ostrovsky@oracle.com
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Replace in linux-next the xen, xen-two, xen-arm with xen/tip.git tree instead.
Date: Tue, 30 Jul 2013 15:53:16 -0400	[thread overview]
Message-ID: <20130730195316.GA12124@phenom.dumpdata.com> (raw)

Hey,

I was wondering if it would be possible to remove from linux-next
the three xen trees and instead use a combined tree, similar to the
x86 tip (so the various maintainers share it)?

The ones that would be removed are:

xen		git	git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git#upstream/xen
xen-two		git	git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git#linux-next
xen-arm		git	git://git.kernel.org/pub/scm/linux/kernel/git/sstabellini/xen.git#linux-next

And instead it would be pulled from:

xen-tip		git	git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git#linux-next

I presume you need Ack's from all of us (so Jeremy and Stefano) so CC-ing them here.

And Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

             reply	other threads:[~2013-07-30 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 19:53 Konrad Rzeszutek Wilk [this message]
2013-07-30 20:26 ` Replace in linux-next the xen, xen-two, xen-arm with xen/tip.git tree instead Jeremy Fitzhardinge
2013-07-31  7:23 ` Stephen Rothwell
2013-07-31 11:19   ` Stefano Stabellini
2013-07-31 11:19     ` Stefano Stabellini
2013-07-31 23:39     ` Stephen Rothwell
2013-07-31 23:39       ` Stephen Rothwell

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=20130730195316.GA12124@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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.