Use the svn status command: svn status | grep ^? Files that are not versioned are indicated with a ? at the start of the line. If you find that you always have some specific files that should not be added to the repository (for example, generated binaries), you should set up the svn:ignore property … Read more
If you want to move the repository and keep history, you’ll probably need filesystem access on both hosts. The simplest solution, if your backend is FSFS (the default on recent versions), is to make a filesystem copy of the entire repository folder. If you have a Berkley DB backend, if you’re not sure of what … Read more
~/.subversion/config or /etc/subversion/config for Mac/Linux and %appdata%\subversion\config for Windows
Have you seen the FAQ entry What if I’m behind a proxy?? … edit your “servers” configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory “~/.subversion”. On Windows it is in “%APPDATA%\Subversion”. (Try “echo %APPDATA%”, note this is … Read more
You can’t directly ignore folders on a checkout, but you can use sparse checkouts in svn 1.5. For example: $ svn co http://subversion/project/trunk my_checkout –depth immediates This will check files and directories from your project trunk into ‘my_checkout’, but not recurse into those directories. Eg: $ cd my_checkout && ls bar/ baz foo xyzzy/ Then … Read more
The single vs. multiple issue comes down to personal or organizational preference. Management of multiple vs. single mainly comes down to access control and maintenance. Access control for a single repository can be contained in a single file; Multiple repositories are may require multiple files. Maintenance has similar issues – one big backup, or a … Read more
You have to upgrade your subversion client to at least 1.7. With the command line client, you have to manually upgrade your working copy format by issuing the command svn upgrade: Upgrading the Working Copy Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the … Read more
I asked myself the same questions when we came to implement Subversion here — about 20 developers spread across 4 – 6 projects. I didn’t find any one good source with ”the answer”. Here are some parts of how our answer has developed over the last 3 years: — commit as often as is useful; … Read more
When you want to look at old files you really should know the difference between: svn cat http://server/svn/project/file -r 1234 and svn cat http://server/svn/project/file@1234 The first version looks at the path that is now available as http://server/svn/project/file and retrieves that file as it was in revision 1234. (So this syntax does not work after a … Read more
Instead of version-controlling the actual configuration file, you could put a template or defaults file in version control, and a script that would ask for DB information and credential to generate the real config file, which would be excluded from (i.e. ignored by) version control. On checkout, developers could run this script to get a … Read more