On Thu, Jul 3, 2014 at 8:02 AM, Daniel Becroft wrote:
> On Thu, Jul 3, 2014 at 4:01 PM, Daniel Becroft wrote:
>>
>> Hi,
>>
>> In the root of our trunk, we have a 'build_tools' folder which is defined
>> as an external.
>>
>> For example
>> /trunk
>> /build_tools (external)
>> /alpha
>>
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 Subversion client. For more details, see
http://subversio
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
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 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
> -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 03, 2014 at 10:58:35AM +0100, No
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
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 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
Hi Stefan,
Thank you for your reply, however at this time I think we're just going to
go ahead with the data I was able to recover and take extra caution as far
as backups are concerned.
Thanks again!
Saurabh
On Wed, Jul 2, 2014 at 3:05 PM, Stefan Sperling wrote:
> On Wed, Jul 02, 2014 at 07:
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)
> 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
> 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
13 matches
Mail list logo
