[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: What will happen if I upgrade from 1.6.x to 1.7.x

From: John Dexter <jdxsolutions_at_gmail.com>
Date: Mon, 25 Mar 2013 13:53:48 +0000

On 25 March 2013 13:36, Simon Large <simon.tortoisesvn_at_gmail.com> wrote:

> On 25 March 2013 12:49, John Dexter <jdxsolutions_at_gmail.com> wrote:
> > I'm running 1.6.8 against an Assembla free repo (I am not sure what
> server
> > version). On a new PC I am testing, I installed the newest Tortoise and
> it
> > wants to upgrade my working copy.
> >
> > However, I also use the codebase on my Mac, which only has svn 1.6 client
> > (and I don't have the inclination to change that right now). In fact
> that is
> > my test PC, I dual boot Win8/OSX 10.8 and want to use the existing Mac
> > working dir rather than check it out twice.
> >
> > So a couple of quick questions:
> >
> > 1)TortoiseSVN 1.7 simply isn't backwards compatible to 1.6 repos?
>
> Any 1.x client is compatible with any 1.x server. However I suspect
> you actually mean working copy when you say repository, in which case
> no, a 1.7 client cannot use a 1.6 WC and vice versa.
>

I think I meant both :) I wasn't sure if a 1.7 working copy could still be
checked in against a 1.6 server, or if I could have a 1.6 WC on one machine
and a 1.7 WC on another machine. It sounds like both those are fine.

>
> > 2)It's 'safe' to get the latest 1.6 version?
>
> Don't understand the question. 1.6 is not the latest version.
>

I meant the last 1.6 version. I wondered if there was ever a reason to keep
the 1.6 client and not upgrade to 1.7, due to server repo version. I think
from your previous answer the asnwer is no, I am safe to upgrade to 1.7.

>
> > 3)Having a shared working dir for dual-boot PC, using svn commandline on
> Mac
> > and Tortoise on Windows... is that a big no-no or should it work?
>
> Big no-no. A working copy should never be shared between 2 different
> OS's. It might work or it might trash the WC. It's fine to access the
> files in both OS's but all subversion operations should always be done
> using the same OS, so for safety you should uninstall Windows SVN
> clients and use only the MAC client, or uninstall MAC SVN clients and
> use only the Windows client.
>

Thanks, this makes sense. I am running parallels on the MAc to get Windows,
so I think I'll stick with Mac SVN commandline on that PC.

Thanks for your help!

John.

>
>
> > Thanks for any help. I am about to take a laptop on my travels so I
> really
> > don't want to screw up my repo, just get things working!
>
> Simon
>
> --
> : ___
> : oo // \\ "De Chelonian Mobile"
> : (_,\/ \_/ \ TortoiseSVN
> : \ \_/_\_/> The coolest Interface to (Sub)Version Control
> : /_/ \_\ http://tortoisesvn.net
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3051882
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3051887

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-03-25 15:54:29 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.