Thanks for the info! I'm pretty much a novice at VCS since I don't really use it to it's full capabilities. I'm sure once my projects grow up that'll change. Heck, I just recently figured out how to block .pyc/sqlite files from being versioned!
> You can erase intermediate commits in a lot of VCS systems. With CVS it is > really easy and even though I haven't tried that with Subversion, I believe it > is easy there as well. I'll look into that. But what I meant was a folder share that tracked disk writes. So I could map the network share as a drive and then just work on it like a local file. Everytime I would write to disk the server would track the changes, and then automatically delete the tracked changes when I commit. That way, I would always the most recent copy of my work, regardless of whether I was on the laptop/desktop/whereever. It would also give me the freedom to only commit when I've finished a change worth noting. No more commit -m "wrong variable name fixed" Although, having a local copy shared via openVPN on the dedicated would almost be the same thing. Provided that I remember to commit often and then delete the intermediate commits. I guess I'm just lazy.
