From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from muon.cran.org.uk (muon.bluestop.org [74.50.51.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 5BD1081E46 for ; Thu, 17 Nov 2016 07:24:18 -0800 (PST) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 61F2C30299; Thu, 17 Nov 2016 15:24:22 +0000 (UTC) Received: from muon.cran.org.uk ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ug_g364c6M-P; Thu, 17 Nov 2016 15:24:21 +0000 (UTC) Received: from [10.0.1.120] (c-73-20-20-155.hsd1.ut.comcast.net [73.20.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Thu, 17 Nov 2016 15:24:21 +0000 (UTC) To: Laszlo Ersek , "edk2-devel (edk2-devel@lists.01.org)" References: <47cd17d8-f022-6ca5-2f52-06a8250f8d14@cran.org.uk> Cc: "Wu, Hao A" , "Ni, Ruiyu" , "Gao, Liming" From: Bruce Cran Message-ID: <886a3cc4-3dcb-db33-cc74-cbe4c6714d09@cran.org.uk> Date: Thu, 17 Nov 2016 08:24:20 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: OVMF: cross-filesystem copy broken? ("The source and destination are the same") X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 15:24:18 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 11/17/2016 2:35 AM, Laszlo Ersek wrote: > There's a patch on the list for said BZ: > [edk2] [PATCH v2] API PathRemoveLastItem not handle root paths properly > > so if the BZ is indeed what you're encountering, then the patch should > fix it for you. Can you please test it and report back in that thread? Unfortunately the patch doesn't fix the problem I'm seeing. -- Bruce