[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-ppc-devel
Subject:    [XenPPC] please pull xenppc-unstable-merge.hg
From:       Hollis Blanchard <hollisb () us ! ibm ! com>
Date:       2007-03-21 23:48:44
Message-ID: 1174520924.32715.58.camel () basalt
[Download RAW message or body]

Hi Keir, please pull from
http://xenbits.xensource.com/ext/xenppc-unstable-merge.hg

I finally have beaten the domain builder into shape, which required a
moving some x86 and ia64 code around. I've also fixed a few other build
and runtime bugs that came down from recent xen-unstable changes.

Separate topic:

At this point, all PowerPC code is merged up. Because I was importing
changesets from xenppc-unstable into xenppc-unstable-merge by hand,
there's a bunch of old history left in xenppc-unstable. I would like to
merge that in. The following commands executed in xen-unstable should do
the right thing:
        hg tip
        hg pull http://xenbits.xensource.com/ext/xenppc-unstable.hg
        HGMERGE=/bin/true hg -y merge
        hg revert -a <old tip>
        hg commit

It looks like that will bring in about 775 changesets without changing
any code, but that's the amount of work you would have gotten all along;
it's just coming in all at once (flooding xen-changelog). Also, not all
of them have proper DCO lines. What do you think?

(In general, I will say that manually importing selected changesets from
a "development" tree into a "merge" tree was a bad idea, and I would be
happy to elaborate for anybody who is considering this model.)

-- 
Hollis Blanchard
IBM Linux Technology Center


_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
[prev in list] [next in list] [prev in thread] [next in thread]