The ultimate/best goal should be xen-ia64-unstable.hg is physically a subtree of
xen-unstable.hg similar to what ia32 tree is now. What ia64 developers checked
into subtree is immediately reflected into xen-unstable.hg, so there will be
much less upstream tree sync issue.
-Fred
Magenheimer, Dan (HP Labs Fort Collins) wrote:
(Changing mailing lists to reply to Tristan's reply to:
http://lists.xensource.com/archives/html/xen-devel/2005-11/msg01271.html
)
With xen-unstable.hg working for Xen/ia64, we need to track changes
on xen-unstable and ensure that it continues to work for Xen/ia64.
xen-ia64-unstable is a "staging" tree, where the Xen/ia64
developers submit patches and new ia64-specific functionality,
but these will always be rolled into xen-unstable about
every week or so.
-----Original Message-----
From: Tristan Gingold [mailto:Tris...@bull.net]
Sent: Wednesday, November 30, 2005 4:46 AM
To: Magenheimer, Dan (HP Labs Fort Collins); Xen Mailing List
Subject: Re: [Xen-devel] RE: Hotplug scripts not working... xen/ia64
domU stopped working
Le Mercredi 30 Novembre 2005 06:50, Magenheimer, Dan (HP Labs Fort
Collins) a écrit :
First binary search step: cset 8054 fails the same way (for
Xen/ia64).
Is it with xen-ia64-unstable.hg tree ?
My current tip is 7922!
Tristan.
2 messages in com.xensource.lists.xen-ia64-develRE: [Xen-ia64-devel] RE: [Xen-devel] ...