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 7EFEE18881 for ; Tue, 25 Aug 2015 15:31:11 +0000 (UTC) Received: (qmail 11732 invoked by uid 500); 25 Aug 2015 15:31:11 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 11682 invoked by uid 500); 25 Aug 2015 15:31:11 -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 11672 invoked by uid 99); 25 Aug 2015 15:31:11 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Aug 2015 15:31:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9AFEE1AAD0F for ; Tue, 25 Aug 2015 15:31:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=qqmail.nl Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 8N_PYDTVFR6K for ; Tue, 25 Aug 2015 15:31:09 +0000 (UTC) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id A1BF0255CA for ; Tue, 25 Aug 2015 15:31:08 +0000 (UTC) Received: by wicja10 with SMTP id ja10so18737765wic.1 for ; Tue, 25 Aug 2015 08:31:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qqmail.nl; s=google; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:thread-index:content-language; bh=W3tjZlPrxrenFmAtx/jz8bsEKs5lL3Ckg2KbWVqITck=; b=XfpLs6zgKEPJmbE9MU9sQ1m9ozDDSpa2NQp0aAXpFpaQpGGcsKLGO+neAfDY09v2G+ TtmIqSmzrgjj35FOtnFyQN4twDSpGP/imCdC5KMIQVBGj9qQbkQmDHQ9r8nB/I3I6FAp kQqQdKzuGAM5GAQhtloreK5zDJjHaht/3bPw0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-type:thread-index:content-language; bh=W3tjZlPrxrenFmAtx/jz8bsEKs5lL3Ckg2KbWVqITck=; b=gvsJbS2bj+DaS6/m2+FlHCxJpLifyoZ7paSr0qUyY4ibADDL4zFbVxKAmzh91FqOjJ HQAjhQstHR7s9Ttqhttw6E4fAQLMkmmlrJsN00ubNezhRg7Th2iRJDE2sVvt/Q7jFkDT liuOREUJR1EMG1brXK/wjIx8wtkFu4ARn9QKYWUBixbarxA/3X3YjvtSbodsCS6usUIC urVyaVpoykdHJ5Q0hs+RUHsqE/z9EjDz9RZbks7hBE752m1ster2/0beWDIDS7diVhVG kX6zxshGoLlEy5kCnkgqj8ztfovTLHRXJCX/S/qjAAOfYtGkhdnzuhdSyyDLamJ9y4tG DE5g== X-Gm-Message-State: ALoCoQlV+ovV7vCU1qPlwqiazRskp+xNDoAm05S+YZIX6g6jHVSkVusLvkPz0InXDcLqLU0OkPk8 X-Received: by 10.180.80.138 with SMTP id r10mr5698673wix.18.1440516667323; Tue, 25 Aug 2015 08:31:07 -0700 (PDT) Received: from i72600 ([2001:610:66e:0:52e5:49ff:fee1:96b7]) by smtp.gmail.com with ESMTPSA id s1sm3166278wix.13.2015.08.25.08.31.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Aug 2015 08:31:06 -0700 (PDT) From: "Bert Huijben" To: "'C. Michael Pilato'" , "'Subversion Development'" References: In-Reply-To: Subject: RE: New 'svn cp --pin-externals' feature compat question. Date: Tue, 25 Aug 2015 17:30:58 +0200 Message-ID: <003301d0df4b$0b5cd980$22168c80$@qqmail.nl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0034_01D0DF5B.CEE6E200" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQItuUU4f/BTtCq0j6F9Cz5XU7vpxp1jItvw Content-Language: nl This is a multipart message in MIME format. ------=_NextPart_000_0034_01D0DF5B.CEE6E200 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, =20 The code actually detects if the definition is in the old or new format = and uses the same format to apply the pegging.=20 See =E2=80=98make_external_description=E2=80=99 which uses = =E2=80=98svn_wc__external_description_format_1=E2=80=99 and = =E2=80=98svn_wc__external_description_format_2=E2=80=99 to handle the = different formats. =20 (In the pre 1.5 format the =E2=80=98-r=E2=80=99 is interpreted as a peg = revision) =20 Bert =20 From: C. Michael Pilato [mailto:cmpilato@collab.net]=20 Sent: dinsdag 25 augustus 2015 17:07 To: Subversion Development Subject: New 'svn cp --pin-externals' feature compat question. =20 I was reading up on the new 'svn cp --pin-externals' feature in the 1.9 = release notes. Great addition, by the way, and one that I hope to use = myself with ViewVC's release tags. =20 One question came to mind, though. The use of the feature appears to = result in pegged externals definitions (as in, @-bearing URLs). That's = great and obviously the correct approach. But if I recall correctly, = this means that use of the feature will cause the copy's externals to be = written in a way that older (pre-1.5) clients do not understand. =20 Is that correct? If so, I think that's a fine limitation to have -- no = complaints at all here. But perhaps this merits a mention in the = Compatibility section of the release notes? =20 -- Mike ------=_NextPart_000_0034_01D0DF5B.CEE6E200 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Hi,

 

The code actually detects if the definition = is in the old or new format and uses the same format to apply the = pegging.

See =E2=80=98make_external_descripti= on=E2=80=99 which uses =E2=80=98svn_wc__external_descri= ption_format_1=E2=80=99 and =E2=80=98svn_wc__external_descri= ption_format_2=E2=80=99 to handle the different = formats.

 

(In the pre 1.5 format the = =E2=80=98-r=E2=80=99 is interpreted as a peg = revision)

 

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = Bert

 

From:<= /b> C. Michael = Pilato [mailto:cmpilato@collab.net]
Sent: dinsdag 25 augustus = 2015 17:07
To: Subversion Development = <dev@subversion.apache.org>
Subject: New 'svn cp = --pin-externals' feature compat = question.

 

I was = reading up on the new 'svn cp --pin-externals' feature in the 1.9 = release notes.  Great addition, by the way, and one that I hope to = use myself with ViewVC's release tags.

 

One question came to mind, though.  The use of = the feature appears to result in pegged externals definitions (as in, = @-bearing URLs).  That's great and obviously the correct = approach.  But if I recall correctly, this means that use of the = feature will cause the copy's externals to be written in a way that = older (pre-1.5) clients do not understand.

 

Is that correct?  If so, I think that's a fine = limitation to have -- no complaints at all here.  But perhaps this = merits a mention in the Compatibility section of the release = notes?

 

-- = Mike

------=_NextPart_000_0034_01D0DF5B.CEE6E200--