3 ms·
> Solo devs maybe. Like I’m gonna bother to set up a Subversion remote for every little repo that I create for myself.
by avgcorrection 4y ago
> Solo devs maybe.
Like I’m gonna bother to set up a Subversion remote for every little repo that I create for myself.
- theamk 4y agoThe most beautiful part of svn, and the one I miss the most in git, is the fact that there is no need to set up tons of separate repo. Every subdirectory acts as a separate git repo. This means you usually only have one svn repo, and you set it up the way you like. As an example, you may set things up so you can checkout: server:/proj/small/hello - to get a single project server:/proj/small- to get all small projects server:/proj - to get all projects If you already have one of those checked out, adding new project is as simple as "mkdir bar", "svn add bar", "svn commit". So juch easier than making new github repo. And multi-level hierarchical project nesting is still something impossible in git.
- avgcorrection 4y ago> So juch easier than making new github repo. Were you paying attention to what I just wrote!? `git init`. What do I need a remote on the Internet for?
- theamk 4y agoDon't you ever share your projects between machines? I at least have laptop, a desktop, and occasional raspberry pi. An ability to have personal projects on both is very handy. It also acts as a nice backup. But yes, if all your work is on one machine, and you have backups of it, there is not much point in svn.
- avgcorrection 4y agoThat’s a file sync. problem, not a VCS problem. And backup is a separate problem.
- Rexxar 4y agoYou don't need internet, you can create the main repo somewhere else on your pc (preferably on a second disk to have very minimal backup) and you use file url to access it "file:///F:/MyRepositoriesAreHere/MyProject-repo/ProjectName/trunk"
- avgcorrection 4y agoThat’s better but still an extra step.