All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: Aron Griffis <aron@hp.com>, xen-devel@lists.xensource.com
Subject: Re: new repo layout?
Date: Thu, 31 May 2007 11:02:05 -0500	[thread overview]
Message-ID: <1180627325.16734.26.camel@basalt> (raw)
In-Reply-To: <1180598644.29571.57.camel@localhost.localdomain>

On Thu, 2007-05-31 at 09:04 +0100, Ian Campbell wrote:
> On Wed, 2007-05-30 at 17:46 -0400, Aron Griffis wrote:
> > Could somebody at XenSource comment on the details of the planned repo
> > changes, i.e. how things will work in the non-sparse world?  For
> > example, what header files will live in the HV vs. the kernel? 
> > Will the HV, tools, kernel typically be built simultaneously as they
> > are now, or will they be built separately?
> 
> From the point of view of someone who has cloned xen-unstable.hg and run
> "make world/dist/etc" there should be no difference in what gets built.
> The current tarball download+unpack+patch+sparse phases will simply be
> replaced by an hg clone phase. There are already options to build other
> trees as well, i.e. "make linux-2.6-paravirt-build" will build the
> latest release of the paravirt_ops tree with Xen support from 
> http://xenbits.xensource.com/ext/paravirt_ops/
> 
> Each OS tree is expected to carry its own set of self-contained headers
> consistent with its needs -- this has always been the case for all trees
> apart from the sparse tree. For the tree which is going to be derived
> from the sparse tree the build will check that the hypervisor headers
> (xen/include/public) and the kernel headers
> (linux-FOO.hg/include/xen/interface/) are in sync and error out in order
> to prevent those two trees diverging.

Hi Ian, when can we expect to see the new Linux tree created? I'm doing
a lot of forward-porting of the PowerPC Linux patches, and so I will
have a few generic Linux patches for the new tree.

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2007-05-31 16: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 [this message]
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
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=1180627325.16734.26.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=Ian.Campbell@XenSource.com \
    --cc=aron@hp.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.