Subversion is a centralized text versioning system, typically used for source code. You can check out any amount of working copies, which are a copy of the repository contents (or a subtree of it) that you can alter at will. If you want to avoid unnecessarily deep directory structures, keep in mind that the specific command matters.
This can be handy when you want to move, merge, or back up repositories, or perhaps to create a new repository with only recent history.
is useful, letting you load the dump into its own directory, meaning you can organize later.
It does expect the mentioned directory to exist, so you'll need to go into a working copy, create and commit it.
It will be consindered missing, won't commit as a delete, and will be restored from the repository's copy with the next update.
To delete it both from versioning and locally: More generally, you can remove changes made at some time by applying the diffs between those versions in reverse.
For example, I had once deleted files between revision 2 and 3 that I actually wanted to keep.
What I want is to reverse all changes made in that revision change: can be used to load in such a dump file into another repository.
See pages like ,  You can also do this on Windows, as a service if you wish; take a look at pages like  and . Repository paths are basically partly a real path to where the repository is stored, and partly a virtual path within the repository contents For example, say I ) must either not exist yet, or be empty.
A repository is a virtual and versioned filesystem; looking at it on the filesystem will show you a bunch of administration files and directories, and the content to come will be stored in a file-based database.
To see what it actually stores - nothing at this point - you need to use a client.
You could now see what's in there (which right now is nothing).