Slow on the uptake here. I find that I'm running version 1.6.17 of Subversion
(SVN) and notice that the current version is 1.7.4.
I'm still on Snow Leopard (10.6.8) on an older Intel Mac Pro and I'm wondering
if there are any "gotchas" with doing the upgrade. The only thing I use with
SVN is BB
The biggest change between 1.6 and 1.7 is the new centralized working
directory. Much like Git, SVN has now gone to a
one-meta-directory-per-workspace concept, instead of the old CVS style
.svn directories in each sub directory.
Generally speaking: you should be able to successfully upgrade witho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/2012 05:13, Steve deRosier wrote:
> The biggest change between 1.6 and 1.7 is the new centralized working
> directory. Much like Git, SVN has now gone to a
> one-meta-directory-per-workspace concept, instead of the old CVS style
> .svn direc
On Mar 31, 2012, at 10:23 PM, Phil Dobbin wrote:
>>
>> Just my 2cp though. Other people might do it differently. Also,
>> unless there's a new feature you want, not doing anything is a
>> perfectly appropriate option, and the one I'd tend to advise.
>
>
> I concur. If it ain't broke, don't fi
On 2 Apr 2012, at 11:47 AM, Bucky Junior wrote:
> I do have some other projects I'm working on where I may put git on a
> separate Linux box to try it out.
Git does not require a server, by the way. It will work with remote
repositories, but if you just want to try it out (or you're not worrie
