Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 20C4D11DB7 for ; Thu, 3 Jul 2014 16:50:55 +0000 (UTC) Received: (qmail 41556 invoked by uid 500); 3 Jul 2014 16:50:54 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 41521 invoked by uid 500); 3 Jul 2014 16:50:54 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 41385 invoked by uid 99); 3 Jul 2014 16:50:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 16:50:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of markphip@gmail.com designates 209.85.219.54 as permitted sender) Received: from [209.85.219.54] (HELO mail-oa0-f54.google.com) (209.85.219.54) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 16:50:50 +0000 Received: by mail-oa0-f54.google.com with SMTP id eb12so520275oac.41 for ; Thu, 03 Jul 2014 09:50:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=muIfU7x1K9fOC1kBTrQL3m7K6w3OA6t+nrss9HoUKAs=; b=BSwlM6TydyGSLiqEbxESaHsnqrt8kpyHQMls/rwwNAXnzs4Eh1DShS+6I5n1Hf/JOP HagpAZYjt+iXIo2Cs9mwciFff9lgXUKAtZH8T8AOrpergtUgvz7GMO6L7CifSVwiwDZ3 90i2Uwr6vY2KQ6TMFT7aEoO3/NDM6SKQaDQP8LOIsa63xzicF58P2WVnQKBoaZN3Dzmn 8Qa4znQbrCF6nQTGRQeEm+D95/hxcH9oUXs3058jafaHv0fRELOPmxcFXg1MHq/K87j9 NQzhX5N35c99c8ZkGGYw95S1iQ9hVerH/nkWZZBP2I7dZRsIGaqZddPG0OFIby4l5zUb TJhw== MIME-Version: 1.0 X-Received: by 10.60.120.98 with SMTP id lb2mr6132242oeb.52.1404406229515; Thu, 03 Jul 2014 09:50:29 -0700 (PDT) Received: by 10.76.13.99 with HTTP; Thu, 3 Jul 2014 09:50:29 -0700 (PDT) In-Reply-To: References: <043e01cf95e0$bd56f7c0$3804e740$@qqmail.nl> <53B525AD.903@wandisco.com> <20140703154731.GB2400@larry.stsp.name> Date: Thu, 3 Jul 2014 12:50:29 -0400 Message-ID: Subject: Re: Extend E155021 message to include supported format version From: Mark Phippard To: Notes Jonny Cc: =?UTF-8?Q?Branko_=C4=8Cibej?= , "users@subversion.apache.org" Content-Type: multipart/alternative; boundary=047d7b339dbd6e44f704fd4cce94 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b339dbd6e44f704fd4cce94 Content-Type: text/plain; charset=UTF-8 On Thu, Jul 3, 2014 at 12:43 PM, Notes Jonny wrote: > Hi Stefan > > > On Thu, Jul 3, 2014 at 4:47 PM, Stefan Sperling wrote: > > On Thu, Jul 03, 2014 at 10:58:35AM +0100, Notes Jonny wrote: > >> I guess the other idea is to promise to only allow ".svn format" > >> updates every 5 years? I can't think that I've noticed any > >> improvements since I've been using new formats.. > > > > The 1.8 format added support for local move tracking, for instance. > > http://subversion.apache.org/docs/release-notes/1.8.html#moves > > > Many thanks for your reply. > > I'm still suffering the version collisions. I was going to join > tortoise svn users list, but I thought as I am already discussing here > I will ask you. > > > I've installed TortoiseSVN 1.7.7 (which uses svn 1.7.5) and it can't > access the checkout from Jenkins (which is supposed to be "1.7" > format). Actually Tortoise is offering to upgrade to "1.7". I am a bit > surprised as it is already a 1.7x release. > Note that Jenkins uses SVNKit, not the Subversion libraries and it has a global preference that indicates which working copy format it will create. I believe it defaults to 1.4, but it can be changed to 1.7 if you are on an updated version of the plugin. I'm a bit confused why TortoiseSVN can't handle. I will probably go > back as a binary search to find a TortoiseSVN that works.. this is > such a high cost on users (already a large amount of money/development > time used up. I'd happy donate an amount of money to get a fixed .svn > standard format for the next decade..) > Why do you need to access the working copies of your continuous integration server with TortoiseSVN? This issue has existed in every Subversion version and I have personally never found it that difficult to manage. Typically on a developer machine it means you either want to upgrade all your SVN clients (command line, TortoiseSVN, IDE integration) together or you just do not try to mix the clients on the same working copy. -- Thanks Mark Phippard http://markphip.blogspot.com/ --047d7b339dbd6e44f704fd4cce94 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, Jul 3, 2014 at 12:43 PM, Notes Jonny <jongmob@gma= il.com> wrote:
Hi Stefan


On Thu, Jul 3, 2014 at 4:47 PM, Stefan Sperling <stsp@elego.de> wrote:
> On Thu, Jul 03, 2014 at 10:58:35AM +0100, Notes Jonny wrote:
>> I guess the other idea is to promise to only allow ".svn form= at"
>> updates every 5 years? I can't think that I've noticed any=
>> improvements since I've been using new formats..
>
> The 1.8 format added support for local move tracking, for instance. > http://subversion.apache.org/docs/release-notes/1.8.= html#moves


Many thanks for your reply.

I'm still suffering the version collisions. I was going to join
tortoise svn users list, but I thought as I am already discussing here
I will ask you.


I've installed TortoiseSVN 1.7.7 (which uses svn 1.7.5) and it can'= t
access the checkout from Jenkins (which is supposed to be "1.7" format). Actually Tortoise is offering to upgrade to "1.7". I am = a bit
surprised as it is already a 1.7x release.

<= div>Note that Jenkins uses SVNKit, not the Subversion libraries and it has = a global preference that indicates which working copy format it will create= . =C2=A0I believe it defaults to 1.4, but it can be changed to 1.7 if you a= re on an updated version of the plugin.

I'm a bit confused why To= rtoiseSVN can't handle. I will probably go
back as a binary search to find a TortoiseSVN that works.. this is
such a high cost on users (already a large amount of money/development
time used up. I'd happy donate an amount of money to get a fixed .svn standard format for the next decade..)

= Why do you need to access the working copies of your continuous integration= server with TortoiseSVN?

This issue has existed i= n every Subversion version and I have personally never found it that diffic= ult to manage. =C2=A0Typically on a developer machine it means you either w= ant to upgrade all your SVN clients (command line, TortoiseSVN, IDE integra= tion) together or you just do not try to mix the clients on the same workin= g copy.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/
--047d7b339dbd6e44f704fd4cce94--