Return-Path: X-Original-To: apmail-subversion-dev-archive@minotaur.apache.org Delivered-To: apmail-subversion-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3340107C2 for ; Thu, 4 Dec 2014 18:53:56 +0000 (UTC) Received: (qmail 65195 invoked by uid 500); 4 Dec 2014 18:53:56 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 65131 invoked by uid 500); 4 Dec 2014 18:53:56 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 65117 invoked by uid 99); 4 Dec 2014 18:53:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2014 18:53:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of brane@wandisco.com designates 209.85.212.174 as permitted sender) Received: from [209.85.212.174] (HELO mail-wi0-f174.google.com) (209.85.212.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2014 18:53:51 +0000 Received: by mail-wi0-f174.google.com with SMTP id h11so35738231wiw.13 for ; Thu, 04 Dec 2014 10:51:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wandisco.com; s=gapps; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hR8YImLciFZcSSLAE9xVuqoTvCI5PN+kz9ghTQmA/Ag=; b=b5bOhpAVqbdhAT5ain98XHBGVrfBfgIi4o902y4uBaqD5/UOKZwMa9IIo1eqIs7zNd qYgGPcFBzdiSncIHfFKGBDrO5KOJb90yFoM7ozKvCrolzrPLuUFyLIE7AuOZhKihvQxq pDyxmy3ZgtCCxB5/qHJ3PJDdVo/6ecjs7Uyig= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hR8YImLciFZcSSLAE9xVuqoTvCI5PN+kz9ghTQmA/Ag=; b=c9NnlIh0zWODBD8sLPQ4hqibCVFhO0Sx4/iV31YOKM7mUH9kkR+AIcODkREb3WOFTs /QerB8SRKawOcA9yPIkNtyFql690CRdVC4ovfRBv5K7cg69VEG+xqnQmfqIHukaWSZdQ JFVwYSvZJ7mB87htDvMzDahDBHE45zA63KX0q0VVN4mF9mqNg6X4drarsqir7yj5EOev gN0AV37lMArUGnc4QT+OLp0cTs5Wm8KCgckrYdO6osb6cadAG8J7kr0wjVfO1bNBZht8 Pf8ezyOS/9zmPkdWpT2kPgeMKQoElj2As8l9UIe32NMe8LHmOiCGpvAnrBOKEo5YQA97 UfxA== X-Gm-Message-State: ALoCoQnAdXzfrUCmpkpoND11ncrW1vqZkPWhBRGuqlgxAgM/nIoMyByVrFF8aiutSLAnViuONVsX X-Received: by 10.181.12.38 with SMTP id en6mr1410291wid.5.1417719119764; Thu, 04 Dec 2014 10:51:59 -0800 (PST) Received: from zulu.23.e-reka.si (cpe-62-84-231-24.dynamic.amis.net. [62.84.231.24]) by mx.google.com with ESMTPSA id u5sm42452857wiz.9.2014.12.04.10.51.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Dec 2014 10:51:58 -0800 (PST) Message-ID: <5480AD4D.9060509@wandisco.com> Date: Thu, 04 Dec 2014 19:51:57 +0100 From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= Organization: WANdisco User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev@subversion.apache.org Subject: Re: Issue #4476 - Mergeinfo containing r0 makes svnsync and svnadmin dump fail References: <1417537985.48137.YahooMailNeo@web87704.mail.ir2.yahoo.com> <1417715744.62760.YahooMailNeo@web87701.mail.ir2.yahoo.com> <1417718445.6392.YahooMailNeo@web87702.mail.ir2.yahoo.com> In-Reply-To: <1417718445.6392.YahooMailNeo@web87702.mail.ir2.yahoo.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 04.12.2014 19:40, Julian Foad wrote: > I (Julian Foad) wrote: > >>> I'll come to 'svnsync' later, but basically my current thought is it >>> should 'correct' the mergeinfo by removing the r0 reference. >> I have written a test for this, and hacked up code to do this by textual >> substitution. It isn't quite right -- for example it would go wrong if a >> path contained the character sequence ":0", among other issues. I >> ought to rewrite it in the form of a proper mergeinfo parser but one that is >> more lenient than the regular parser. > Here's the patch in progress... ... no it isn't! :) -- Brane