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

Auto Upgrade Behavior

From: Paul Burba <ptburba_at_gmail.com>
Date: Fri, 24 Aug 2012 17:21:09 -0400

Currently trunk tries to auto-upgrade the WC pretty much every chance
it gets, even when the cwd is an unversioned directory within a WC.
I've been wondering if this is really such a good idea -- it's been
quite noticeable, in an annoying way, while working on the
inheritable-props branch.

What happens is this:

1) I check out the iprops branch with a Subversion 1.7.6 client (WC
format 29) to C:\SVN\src-trunk-2)

2) I build the iprops branch, which is using WC format 30.

3) From the root of my iprop WC I run the test suite. The first
checkout done as part of the test auto-upgrades the WC rooted at
C:\SVN\src-trunk-2 to format 30, even though the cwd of the checkout
is an unversioned directory
(C:\SVN\src-trunk-2\Debug\subversion\tests\cmdline) and the checkout
target is below that
(C:\SVN\src-trunk-2\Debug\subversion\tests\cmdline\svn-test-work\working_copies\basic_tests-1).

Pretty much any command with an unversioned directory under an older
format WC root will attempt to upgrade that root.

Probably not a huge problem for anyone who is not a Subversion
developer, but it's something we might want to keep in mind as we bump
the WC format in the future.

-- 
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Skype: ptburba
Received on 2012-08-24 23:21:41 CEST

This is an archived mail posted to the Subversion Dev mailing list.