On Tue, Mar 22, 2016 at 6:47 AM, Stefan Sperling wrote:
> On Tue, Mar 22, 2016 at 12:25:42AM -0400, Nico Kadel-Garcia wrote:
>> Then, when ready to switchover, make a good backup of the old system,
>> *LOCK IT* to prevent any further ocmmits, and switch services to the
>> new server. You should be
Bert Huijben wrote:
>I'm not sure where you read that, but subversion can upgrade working copies
>all the way up from 1.0. (See our compatibility guarantee)
perhapse here:
http://subversion.apache.org/docs/release-notes/1.9.html#wc-upgrade
>>Subversion 1.9 can only upgrade working copies created
On Tue, Mar 22, 2016 at 12:25:42AM -0400, Nico Kadel-Garcia wrote:
> Then, when ready to switchover, make a good backup of the old system,
> *LOCK IT* to prevent any further ocmmits, and switch services to the
> new server. You should be able to activate a proxy or port forwarding
> for the old ser
I'm not sure where you read that, but subversion can upgrade working copies
all the way up from 1.0. (See our compatibility guarantee)
There is one exception: If a working copy operation was stopped halfway. in
this case you need to run 'svn cleanup' with your older Subversion version
(or 1.6.x
On Mon, Mar 21, 2016 at 3:58 PM, Stefan Sperling wrote:
> On Mon, Mar 21, 2016 at 10:33:49AM -0700, Safarulla Meerasahib wrote:
>> Hi,
>>
>>
>>
>> We have recently taken over a production application from other team, which
>> uses the SVN 1.5.0 as one of the component. Now we have a requirement
Stefan Sperling wrote on Mon, Mar 21, 2016 at 20:58:37 +0100:
> On Mon, Mar 21, 2016 at 10:33:49AM -0700, Safarulla Meerasahib wrote:
> > Hi,
> >
> >
> >
> > We have recently taken over a production application from other team,
> > which uses the SVN 1.5.0 as one of the component. Now we have
On Mon, Mar 21, 2016 at 10:33:49AM -0700, Safarulla Meerasahib wrote:
> Hi,
>
>
>
> We have recently taken over a production application from other team, which
> uses the SVN 1.5.0 as one of the component. Now we have a requirement to
> upgrade this to latest version of the subversion.
>
>
> On Mar 21, 2016, at 10:33 AM, Safarulla Meerasahib
> wrote:
>
> Hi,
>
> We have recently taken over a production application from other team, which
> uses the SVN 1.5.0 as one of the component. Now we have a requirement to
> upgrade this to latest version of the subversion.
> While going
