-----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 directories in each sub directory. > > Generally speaking: you should be able to successfully upgrade without > much trouble. To do it cleanly though: > 1. Get all your working areas committed to your SVN server. > 2. Remove your working areas > 3. Backup your SVN server > 4. Upgrade your SVN server (there should be appropriate steps in the SVN docs) > 5. Upgrade your SVN client > 6. Checkout new working areas > > Obviously, non-dependent steps can be done in other orders. > > 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 fix it. If I was still using svn, I'd stay put at 1.6 & any update/change would be to move to git. YMMV. Cheers, Phil... > On Sat, Mar 31, 2012 at 8:45 PM, Bucky Junior > <[email protected]> wrote: >> 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 BBEdit and I only use it to track my own versions of what >> I'm writing. No one else is involved. >> >> Are there any hints and tips that I need to pay attention to while I'm >> upgrading? - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPd9g3AAoJEKpMeDHWT5ADu4QH/19F/xhNgSXjcS/W3jddhyu/ NelSBkIdjIXKwYAoWgjAaoA0lFqRmMYLLMS0IwJJGUmQLDAOwc6D49P6Hu+ELQBd TBLqeoYSMy7w+91lqj7l0qwavzCOAAKte2yAx8S2buoGdE9yEOB2tgQZPzmrGV9m sExSK+7KpFBLBdqqQbqrOzLQ+nrai2Royh8SY5UoJln9d+rD8TOQUQ8ggbBl5sR+ 1j2rrLIJx4wU+HKaSB/8UavTiUuNE70mn2eWPgA/BF7Z63rQd5IdSMoinJ923BGH bDrmv1fBfZzUEgTPh+yRnbRYpOXiuIM+N1zGAmoSPVmexNnwpZXqoBOjdZBL7VI= =5iqn -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
