That is to say, you can use a 1.7 client with an older server, and you can use a 1.7 server with older clients. Older clients and servers interoperate transparently with 1.7 servers and clients. If you need to use multiple clients on the same working copy then be sure that you can update all the clients before upgrading the working copy. Migrating to 1.7 working copies must be considered a one-way operation. Pre-1.7 clients cannot access 1.7 working copies at all and there is no downgrade option. Because the working copy format has changed with this release, 1.7 clients cannot access an earlier working copy without first upgrading it. TortoiseSVN, AnkhSVN, and the SVN command line client. Subversion working copies are sometimes accessed using several different clients, e.g. When the branch/tag is created from the working copy, the properties are modified first, then the branch/tag is created and then the properties are changed back to their original value.Ĭompatibility concerns Local Client Compatibility This will create additional commits for each property. When the branch/tag is created from HEAD or a specific revision in the repository, TortoiseSVN first creates the branch/tag, then adjusts the properties. If externals are set to an explicit revision when creating a branch or tag, TortoiseSVN automatically changes the svn:externals property. The branch/tag dialog now allows you to tag the externals too. If the svn:externals are not tagged too, a later checkout from the created tag would fetch the HEAD revision of the external, which can lead to inconsistent builds if the external got additional commits. When creating a branch or tag, the svn:externals properties are branched/tagged as they are, usually pointing to the HEAD revision of another repository or even the same repository but different path.
0 kommentar(er)
