This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] the latest dom0 tree

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] the latest dom0 tree
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Fri, 24 Apr 2009 09:51:12 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, M A Young <m.a.young@xxxxxxxxxxxx>
Delivery-date: Thu, 23 Apr 2009 18:52:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49F0A3D0.9030409@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E2263E4A5B2284449EEBD0AAB751098401D184852A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.GSO.2.00.0904201124420.3323@xxxxxxxxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401D1848634@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49F0A3D0.9030409@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnEOBZF1vZe6NSvSiG5s0XFgCD3lQARwtfA
Thread-topic: [Xen-devel] the latest dom0 tree
Thanks. I will do that.


Jeremy Fitzhardinge wrote:
> Jiang, Yunhong wrote:
>> Thanks for your information. Seems xen-tip/next is changed
> in April 14 while push2/xen/dom0/master is still in Mar 29.
> Can I assume all patch is hackery or push2/xen/dom0/master is
> in xen-tip/next already? If yes, I will base my patch on xen-tip/next.
> Yes, that would work.  Though preferably you could base your topic
> branch on the most appropriate topic branch and work on that (so that
> unrelated upstream changes don't have an impact on your work).
>    J
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>