[XenPPC] Re: patch flow

[Hollis Blanchard <hollisb@xxxxxxxxxx>]

On Sun, 2006-12-17 at 18:00 +0000, Xen patchbot-xenppc-unstable wrote:
> # HG changeset patch
> # User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
> # Node ID b04e24db308f2215c6bafaf358d1c10da79f244f
> # Parent  965d3e42dddaf5971001f7d172d192f925537644
> [XEN][POWERPC] get cpu_*_maps correct so physinfo and affinity is accurate
> 
> Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>

Please commit all uncontroversial patches first to xenppc-merge, then
pull xenppc-merge into xenppc-unstable. It's OK if we change our minds
later and revert changesets in -merge.

To recap, xenppc-merge contains patches going upstream; it is pulled
directly into xen-unstable. xenppc-unstable is xen-unstable plus any
temporary hacks we need to make progress. (When you define
xenppc-unstable this way, it obviously should be a child tree, not a
parent tree.)

This will ensure that we never have the same difficulty staying in sync
with xen-unstable that we've had in the past.

-- 
Hollis Blanchard
IBM Linux Technology Center


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