working-copy

I have a large Subversion repository with nearly 15 GB of data spread across ~500,000 files. Now I need to check out this repository to a remote host which would take days to complete. The host I'm checking out to already has a complete copy of the data in the repository. But seeing as the files weren't checked out directly from the repository, they do not constitute a working copy (no ".svn" folders). I'd like to avoid copying all this data across the network, especially when it already exists on the target host. Is there a trick I can use that will turn a preexisting directory into a working

I'd like to know how can I set two repositories for my one working copy. I need one repository in my server, so that I can check in/out between two pcs; I need another repository in my local pc, so that I can see the result of diff quickly (my svn server is on a slow shared host) How can I do that? Have a look at repository replication . You can set up a cron job to periodically synch from one repository to the other. But you have to make sure that commits only happen to one of the two. If commits will happen to both repositories, maybe a distributed versioning system such as git , Bazaar or

I'm trying to svn checkout into my public_html folder, but I get this error: svn: '.' is already a working copy for a different URL My brother already set up a boiler plate site for me, but I've changed it and put those changes into a repo of my own. How do I make this folder not be a working copy of the repo he set up originally? Can I delete the public_html folder and make a new one? I'm fine with starting from scratch, as I'm going to just checkout an already installed drupal site onto this site. I saw in another question that a solution may be to simply delete the .svn directory. I tried

For example, the SVN 1.5 client has one layout for working copies, and the SVN 1.6 client has a different layout. I understand that the layout automatically gets upgraded when it gets touched by a newer client. If I have a working copy on my system, how can I find out the version of the layout it's using? Filip Navara If .svn/format exists, then read the number in it: Version 7 is SVN 1.3 Version 8 is SVN 1.4 Version 9 is SVN 1.5 If .svn/format doesn't exist then the version number is on the first line in .svn/entries : Version 10 is SVN 1.6 Version 12 is SVN 1.7 Subversion 1.6 was the first

I have a working copy repository that I've been working in no problem; the origin for this repository is on GitHub. I'd like to make my working copy repository available as the origin for my build machine (a VM on another physical host), so that commits I make to my working copy can be built and tested on the build machine without having to go via GitHub first. I already have a build for the GitHub repository going, but I'd like this to be a "golden" repository/build; i.e., if something goes in there, the build against GitHub should be guaranteed to pass. I've looked at the documentation on