svnadmin

Yes, you can also go in with SVN and obliterate history too, using svnadmin dump and svnadmin load.

The exact script does the following: svnadmin dump d:\repo > repo.dump The output from svnadmin has a lot of lines.

Other SCMs limit mutations to additions and use a separate command (svnadmin) to do things that may permanently lose information.

For example, an svnadmin dump piped to a file which takes 8 mins in cmd.exe takes 14 hours in powershell...

Nice - that'll spice up my rather boring svnadmin dump sessions - thanks for posting!

You can do the split in subversion by filtering the paths, and keeping the history:-) There is a svnadmin command for that.

As I remember, svn is more complicated, it has that separate svnadmin tool and relies on you to craft a suitable directory structure.

When you fucked up history and you want to change it, there are some simple git commands to do this and some very, very tedious svnadmin commands to do this.

SVN is very, very easy to set up and use: svnadmin create ~/svn-repo svn import myproject file:///home/you/svn-repo/myproject svn co file:///home/you/myproject myproject-workingcopy Work in the working copy as you would on any SVN project.

With svn, you can just "svnadmin dump", edit the file in your text editor, and "svnadmin load".

You're of course completely correct; I can remove history by using "svnadmin dump", or editing the RCS files backing CVS, or probably hacking Perforce's BDB file manually.