You need to determine whether this is a problem with TortoiseSVN, your Subversion repository, or your network connection. First of all, check your URL. I never used User-Friendly SVN, so I don’t know what it does to the Apache httpd configuration. However, the standard Apache configuration for multiple repositories is usually http://<server>/svn/<module> and not http://<server>/svn/usvn/<module>. … Read more
One approach would be to: Copy edited items to another location. Delete the folder containing the problem path. Update the containing folder through Subversion. Copy your files back or merge changes as needed. Commit Another option would be to delete the top level folder and check out again. Hopefully it doesn’t come to that though.
What’s the first part of your Subversion repository URL? If your URL looks like: http://subversion/repos/, then you’re probably going over Port 80. If your URL looks like: https://subversion/repos/, then you’re probably going over Port 443. If your URL looks like: svn://subversion/, then you’re probably going over Port 3690. If your URL looks like: svn+ssh://subversion/repos/, then you’re probably going over Port 22. If your … Read more
TortoiseSVN now includes those in their install file (or atleast it did when I installed it 5/23/2012) During the options of what to choose to install i had to click on the command line tools. Now it is in (tortoisesvnInstallfolder)\bin\svnadmin.exe just thought i’d share
Here are some sections about it in the svnbook / TortoiseSVN manual: This is the svnbook page on svn:externals. It is the most useful resource on the subject. This one explains four ways to include sub-projects in the workflow (and in the process misses a fifth one: symlinks). And this last one is a TortoiseSVN-specific page on how to … Read more