RE: [Xen-merge] xen-merge mailing list

[Rik van Riel <riel@xxxxxxxxxx>]

On Tue, 2 Aug 2005, Ian Pratt wrote:

> The first part of the work is going to be rearranging our sparse tree to
> split arch/xen out in to drivers/xen/core and arch/{i386/x86_64}/xen.
> Patches for this step would be very messy (mostly file renames) and
> aren't worth maintaining as patches, hence the Linux hg tree. 

Could we do the move of non-arch specific code from
arch/xen to drivers/xen/core in the current Xen
linux-sparse tree already ?

We can then do the other bits gradually.

My main worry is that we would end up with an alternative
tree that has an obsolete version of Xen that's mergeable
upstream - and no way to merge that tree with the current
Xen bits.

-- 
The Theory of Escalating Commitment: "The cost of continuing mistakes is
borne by others, while the cost of admitting mistakes is borne by yourself."
  -- Joseph Stiglitz, Nobel Laureate in Economics

_______________________________________________
Xen-merge mailing list
Xen-merge@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-merge