From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: the latest dom0 tree
Date: Thu, 23 Apr 2009 10:22:24 -0700
Message-ID: <49F0A3D0.9030409@goop.org>
References: <E2263E4A5B2284449EEBD0AAB751098401D184852A@PDSMSX501.ccr.corp.intel.com>	<alpine.GSO.2.00.0904201124420.3323@algedi.dur.ac.uk>
	<E2263E4A5B2284449EEBD0AAB751098401D1848634@PDSMSX501.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401D1848634@PDSMSX501.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>, M A Young <m.a.young@durham.ac.uk>
List-Id: xen-devel@lists.xenproject.org

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