On Fri, Dec 16, 2011 at 01:53:21PM -0500, Adam Walling wrote:
> When creating a new branch, obviously everyone will need to download it for
> maintenance and etc. The naive approach is to simply update and download
> the new branch from the server. However, with a large branch and with many
> users simultaneously updating, this quickly overloads the bandwidth and may
> end up takings hours to complete.
>
> With 1.6, we would take advantage of being able to copy all of trunk to the
> new branch directory on the local filesystem, and then switch to the actual
> branch URL and update, therefore only transferring files that actually
> differ. This is pretty much the process touched upon in the svnbook
> http://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html
>
> In 1.7 this does not seem to be possible, since there are no entries in the
> database for the local copies.
I am not sure why you are seeing a problem here.
1.7 working copies can be copied and then switched. Just be careful not
to copy the sqlite database (.svn/wc.db) while it is being accessed.
See http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng
What are you basing your assumption on?
Did you try out your procedure with 1.7 and run into some problem?
Received on 2011-12-16 20:12:52 CET