From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Egger Subject: Re: [PATCH] libxl: blktap2 portiblity fixes Date: Tue, 27 Jul 2010 14:07:26 +0200 Message-ID: <201007271407.27558.Christoph.Egger@amd.com> References: <201007201831.21416.Christoph.Egger@amd.com> <201007261805.06746.Christoph.Egger@amd.com> <19533.47528.342464.491827@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19533.47528.342464.491827@mariner.uk.xensource.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Monday 26 July 2010 18:36:56 Ian Jackson wrote: > Christoph Egger writes ("Re: [Xen-devel] [PATCH] libxl: blktap2 portiblity fixes"): > > On Monday 26 July 2010 16:53:02 Ian Jackson wrote: > > > Christoph Egger writes ("Re: [Xen-devel] [PATCH] libxl: blktap2 > > > portiblity > > > > fixes"): > > > > Can you use the c/s numbers, please? > > > > > > Changeset numbers are not guaranteed to be meaningful outside a > > > particular tree, particularly in the presence of merges. > > > > > > > It was not necessary to backout c/s 21834 as this wasn't the root > > > > cause. > > > > > > I think by 21834 you mean 24277e3237ca. > > > > No, c/s 21834 has the hash e76befc7fe2d. > > Thus proving my point. In my tree 21834 is 24277e3237ca :-). I am not refering the c/s to my local tree. I'm refering the c/s to http://xenbits.xensource.com/staging/xen-unstable.hg/ Christoph -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632