All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: xen-devel@lists.xensource.com,
	James Bulpin <James.Bulpin@cl.cam.ac.uk>,
	Aron Griffis <aron@hp.com>,
	Ian Campbell <Ian.Campbell@XenSource.com>,
	xen-ppc-devel <xen-ppc-devel@lists.xensource.com>,
	xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: new repo layout?
Date: Mon, 04 Jun 2007 13:02:41 -0600	[thread overview]
Message-ID: <1180983761.6221.160.camel@bling> (raw)
In-Reply-To: <1180979173.29109.4.camel@basalt>

On Mon, 2007-06-04 at 12:46 -0500, Hollis Blanchard wrote:
> On Mon, 2007-06-04 at 11:25 -0600, Alex Williamson wrote:
> > 
> > > Another option would be to move the ia64 and ppc trees into separate
> > > subdirectories of /ext/. I'm open to other alternatives.
> > 
> >    So far, this sounds like the best option.  This way it would work
> > just like the staging tree builds and would hopefully be less likely
> > to get broken.  We might also gain some flexibility in being able to
> > create new repos in the subdirectory.  Thanks,
> 
> If you're suggesting moving all PPC repositories, including the Linux
> tree, into http://xenbits.xensource.com/ext/powerpc/ , then that's fine
> with me.

  Yep, I think this is the way to go.  So we'll have:

http://xenbits.xensource.com/ext/powerpc/
http://xenbits.xensource.com/ext/ia64/

Each will have a linux-2.6.18-xen.hg repo in it that will be maintained
by the arch maintainers and used for pulls into upstream.  The default
arch Xen branch needs to be moved into the directory as well.  I also
think it might be good to standardize on names.  I'd like the
xen-ia64-unstable.hg repo to be renamed to xen-unstable.hg.  This way
we'll end up with common names like:

/xen-unstable.hg
/linux-2.6.18-xen.hg
/staging/xen-unstable.hg
/staging/linux-2.6.18-xen.hg
/ext/ia64/xen-unstable.hg
/ext/ia64/linux-2.6.18-xen.hg

Sound good?  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

  reply	other threads:[~2007-06-04 19:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 21:46 new repo layout? Aron Griffis
2007-05-31  8:04 ` Ian Campbell
2007-05-31 16:02   ` Hollis Blanchard
2007-05-31 16:23     ` Ian Campbell
2007-06-04 14:39       ` Alex Williamson
2007-06-04 16:14         ` Ian Campbell
2007-06-04 17:25           ` Alex Williamson
2007-06-04 17:46             ` Hollis Blanchard
2007-06-04 19:02               ` Alex Williamson [this message]
2007-06-04 19:15                 ` Hollis Blanchard
2007-06-04 21:38                   ` Ian Campbell
2007-06-04 21:41                     ` Alex Williamson
2007-06-18 17:40                     ` Re: [Xen-devel] " Jimi Xenidis
2007-06-18 18:14                       ` [XenPPC] " Ian Campbell
2007-06-18 19:19                         ` James Bulpin
2007-06-18 19:23                           ` Re: [Xen-devel] " Jimi Xenidis
2007-06-18 19:26                           ` [XenPPC] " Jimmy Markakis
2007-06-18 20:00                             ` [XenPPC] " Hollis Blanchard

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=1180983761.6221.160.camel@bling \
    --to=alex.williamson@hp.com \
    --cc=Ian.Campbell@XenSource.com \
    --cc=James.Bulpin@cl.cam.ac.uk \
    --cc=aron@hp.com \
    --cc=hollisb@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    --cc=xen-ppc-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.