On Fri, Jul 4, 2014 at 4:51 PM, Andy Levy wrote:
> On Fri, Jul 4, 2014 at 11:16 AM, Notes Jonny wrote:
>> Hi Mark
>>
>> You are right that I did have 1.8.x installed. Which I downgraded to
>> this version:
>>
>> TortoiseSVN 1.7.7, Build 22907 - 32 Bit , 2012/05/15 12:16:05
>> Subversion 1.7.5,
>>
On Mon, Jul 7, 2014 at 9:40 AM, Notes Jonny wrote:
> On Fri, Jul 4, 2014 at 4:51 PM, Andy Levy wrote:
>> On Fri, Jul 4, 2014 at 11:16 AM, Notes Jonny wrote:
>>> Hi Mark
>>>
>>> You are right that I did have 1.8.x installed. Which I downgraded to
>>> this version:
>>>
>>> TortoiseSVN 1.7.7, Build
On Fri, Jul 4, 2014 at 11:16 AM, Notes Jonny wrote:
> Hi Mark
>
> You are right that I did have 1.8.x installed. Which I downgraded to
> this version:
>
> TortoiseSVN 1.7.7, Build 22907 - 32 Bit , 2012/05/15 12:16:05
> Subversion 1.7.5,
> apr 1.4.6
> apr-utils 1.3.12
> neon 0.29.6
> OpenSSL 1.0.1
On Fri, Jul 4, 2014 at 11:16 AM, Notes Jonny wrote:
> Hi Mark
>
> You are right that I did have 1.8.x installed. Which I downgraded to
> this version:
>
> TortoiseSVN 1.7.7, Build 22907 - 32 Bit , 2012/05/15 12:16:05
> Subversion 1.7.5,
> apr 1.4.6
> apr-utils 1.3.12
> neon 0.29.6
> OpenSSL 1.0.1c
Hi Mark
You are right that I did have 1.8.x installed. Which I downgraded to
this version:
TortoiseSVN 1.7.7, Build 22907 - 32 Bit , 2012/05/15 12:16:05
Subversion 1.7.5,
apr 1.4.6
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.1c 10 May 2012
zlib 1.2.7
NB. I don't know why tortoise is called 1.7.7 an
> Interesting. I have set it as 1.7 in the "Manage Jenkins", which means
> it works with 1.7.5 cygwin svn client. But not 1.7.7 TortoiseSVN..
I think you have TortoiseSVN 1.8.7 installed. That would make sense since it is
current version and it would explain your problems. That would be SVN 1.8
> On Jul 3, 2014, at 3:01 PM, Notes Jonny wrote:
>
> Hi Mark
>
>> On Thu, Jul 3, 2014 at 5:50 PM, Mark Phippard wrote:
>>> 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 a
On 03.07.2014 21:01, Notes Jonny wrote:
> Why do you need to access the working copies of your continuous integration
> server with TortoiseSVN?
> On Jenkins machine it has some steps:
>
> A) Jenkins SVN checkout
> B) Jenkins Triggers build
> C) Jenkins Triggers automated testing of the build.
> D)
Hi Mark
On Thu, Jul 3, 2014 at 5:50 PM, Mark Phippard wrote:
> 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
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
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
> -Original Message-
> From: Stefan Sperling [mailto:s...@elego.de]
> Sent: 03 July 2014 16:48
> To: Notes Jonny
> Cc: Branko Čibej; users@subversion.apache.org
> Subject: Re: Extend E155021 message to include supported
> format version
>
> On Thu, Jul 0
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
Hi Brane
On Thu, Jul 3, 2014 at 10:43 AM, Branko Čibej wrote:
> On 03.07.2014 11:37, Notes Jonny wrote:
>
> Hi Bert
>
> Could I ask, would it be possible to standardise the .svn format to
> avoid the problems I see?
>
>
> svn: E155021: This client is too old to work with the working copy at
> '/c
On 03.07.2014 11:37, Notes Jonny wrote:
> Hi Bert
>
> Could I ask, would it be possible to standardise the .svn format to
> avoid the problems I see?
>
>
> svn: E155021: This client is too old to work with the working copy at
> '/cygdrive/c/jenkins/_code' (format 31).
> You need to get a newer Subv
To: users@subversion.apache.org
>>> Subject: Extend E155021 message to include supported format version
>>>
>>> Hello
>>>
>>> I raised this ticket. Ben Reser suggested to discuss on here in the
>>> first instance
>>>
>>> http:
org
>> Subject: Extend E155021 message to include supported format version
>>
>> Hello
>>
>> I raised this ticket. Ben Reser suggested to discuss on here in the
>> first instance
>>
>> http://subversion.tigris.org/issues/show_bug.cgi?id=4511
>>
> -Original Message-
> From: Notes Jonny [mailto:jong...@gmail.com]
> Sent: woensdag 2 juli 2014 11:45
> To: users@subversion.apache.org
> Subject: Extend E155021 message to include supported format version
>
> Hello
>
> I raised this ticket. Ben Reser sugg
Hello
I raised this ticket. Ben Reser suggested to discuss on here in the
first instance
http://subversion.tigris.org/issues/show_bug.cgi?id=4511
Extend E155021 message to include supported format version
svn, version 1.7.5 (r1336830)
Could error message E155021 be extended please to include
19 matches
Mail list logo
