$ mkdir repos
$ svnadmin create repos/test
$ svn co file://`pwd`/repos/test
$ ls -a test/
. .. .svn
Localhost can be a server for svn too; you just can't store the repo metadata in the same folder as the working copy. For single-developer projects being maintained on one machine, though, it works well enough.
Note that I'm not actually advocating this solution; just pointing out that it exists.
As I said when you're looking at your files it's not obvious what branch you're on. On my command prompt (PS1 string) I display that. So as I navigate a project I know which branch I'm on at all times.
I'd find it inconvenient. Just this morning I had to checkout a random commit, run a test (kinda like a bisect) and then see what changed between adjacent commits to see if I can suss out a bug.
From the command line that's all keyboard easy. From pointy-clicky you'd need to switch into some tree viewer, check out the commit, go back to the command prompt, run the tests, etc...
5
u/[deleted] Jun 19 '14
I don't have any branches. So now what?