WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[XenPPC] Re: [Xen-devel] Xen 3.1.1 -- initial patchqueue

To: Ben Guthro <bguthro@xxxxxxxxxxxxxxx>
Subject: [XenPPC] Re: [Xen-devel] Xen 3.1.1 -- initial patchqueue
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 10 Sep 2007 13:56:04 +0100
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Sep 2007 05:56:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46E53D15.20906@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfzqfIXMPJLcF+dEdy8TgAX8io7RQ==
Thread-topic: [Xen-devel] Xen 3.1.1 -- initial patchqueue
User-agent: Microsoft-Entourage/11.3.6.070618
Or mercurial has a dependency that behaves differently on your system. This
patchqueue is only temporary until the 3.1.1 release -- I'd just modify that
one patch in your private repo to exclude the troublesome character.

 -- Keir

On 10/9/07 13:48, "Ben Guthro" <bguthro@xxxxxxxxxxxxxxx> wrote:

> 
> Keir Fraser wrote:
>> We're using mercurial patchqueues. Mercurial version 0.9.1. I've just cloned
>> and applied the patch queue from scratch with no problems.
>> 
>>  -- Keir
>>   
> Perhaps it is a regression in the behavior of hg? I am using 0.9.3, and
> cannot get the patch queue to apply:
> 
> 
> [bguthro@bguthro dev]$ rm -rf xen-3.1.hg/
> [bguthro@bguthro dev]$ hg clone -q
> http://xenbits.xensource.com/xen-3.1-testing.hg xen-3.1.1.hg
> abort: destination 'xen-3.1.1.hg' already exists
> [bguthro@bguthro dev]$ rm -rf xen-3.1.1.hg/
> [bguthro@bguthro dev]$ hg clone -q
> http://xenbits.xensource.com/xen-3.1-testing.hg xen-3.1.1.hg
> [bguthro@bguthro dev]$ cd xen-3.1.1.hg/.hg
> [bguthro@bguthro .hg]$ hg clone -q
> http://xenbits.xensource.com/xen-3.1-testing.pq.hg patches
> [bguthro@bguthro .hg]$ cd ..
> [bguthro@bguthro xen-3.1.1.hg]$ hg qpush -a
> applying 15023-6e597e529fea
> applying 15035-23c4790512db
> applying 15038-e19ddfa781c5
> applying 15039-60240a72e2b2
> applying 15043-759d924af6d8
> applying 15044-03a13457d993
> applying 15045-5f6da38ff828
> applying 15046-e527b4ff1948
> applying 15048-e33cce8fa400
> applying 15049-174995130550
> applying 15051-384a29655270
> applying 15052-65ce4866d20b
> applying 15053-3ecf51689671
> applying 15056-a605044ecb33
> applying 15057-75b4c7cb007d
> applying 15058-3581a77791e3
> applying 15061-05ea0d79a92f
> applying 15062-b2adb797900a
> applying 15063-807f374e720d
> applying 15064-eb027b704dc5
> applying 15065-f4390e34ad12
> applying 15066-9e9c09c75110
> applying 15067-c027880b50b4
> applying 15068-dc4324d3fbb0
> applying 15069-cb006eecd6f5
> applying 15070-fbce94a9feaa
> applying 15072-d4a0706d6747
> applying 15073-e1f43038f1d8
> applying 15074-5c7a1e3abd54
> applying 15075-5efb46bfbcac
> applying 15076-9ec165fa8128
> applying 15077-711bfe07999b
> applying 15078-6145e5508d6b
> abort: decoding near 'Ingard Mev�g <ingard': 'utf8' codec can't decode
> bytes in position 186-188: invalid data!
> transaction abort!
> rollback completed
> [bguthro@bguthro xen-3.1.1.hg]$ hg --version
> Mercurial Distributed SCM (version 0.9.3)
> 
> Copyright (C) 2005, 2006 Matt Mackall <mpm@xxxxxxxxxxx>
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 



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