All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: Aron Griffis <aron@hp.com>,
	xen-devel@lists.xensource.com,
	Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: new repo layout?
Date: Mon, 04 Jun 2007 11:25:28 -0600	[thread overview]
Message-ID: <1180977928.6221.144.camel@bling> (raw)
In-Reply-To: <1180973667.4041.18.camel@localhost.localdomain>

Hi Ian,

On Mon, 2007-06-04 at 17:14 +0100, Ian Campbell wrote:
> 
> Hmm.
> 
> xen-unstable will look at a URL derived from it's own parent to find the
> Linux tree this means that for the ppc and ia64 trees it will currently
> be looking on xenbits for /ext/linux-2.6.18-xen.hg for both archs, this
> tree doesn't even exist and I don't think you'll want to share a Linux
> tree.

   Agreed, synchronizing updates and pulls would be too much of a
headache.

> If we define $(XEN_LINUX_ARCH) as "" in the $(XEN_TARGET_ARCH)==x86*
> case and -$(XEN_TARGET_ARCH) in != x86 case. Mixing that into
> XEN_LINUX_HGREPO would yield /ext/linux-2.6.18-xen-ia64.hg etc. Does
> that seem OK to you?

  But that would only need to be the case if the parent of the xen tree
contained xenbits.xensource.com/ext in the path (or some other locally
defined path if the parent is a local clone).  If we're building
xen-unstable.hg on ia64, it needs to pull linux-2.6.18-xen.hg just as it
would on x86.  This quickly starts to sound like rather complicated
rules.

> 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,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

  reply	other threads:[~2007-06-04 17:25 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 [this message]
2007-06-04 17:46             ` Hollis Blanchard
2007-06-04 19:02               ` Alex Williamson
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=1180977928.6221.144.camel@bling \
    --to=alex.williamson@hp.com \
    --cc=Ian.Campbell@XenSource.com \
    --cc=aron@hp.com \
    --cc=hollisb@us.ibm.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.