4 ms·

Don't you think that git's advantage over SVN evaporates when there is only one user on a team? I run my private Subversion repository which I use for everythin

by tx 19y ago

Don't you think that git's advantage over SVN evaporates when there is only one user on a team? I run my private Subversion repository which I use for everything (not just code), I looked at git, and while I see the benefits for large teams, I simply couldn't justify the switch. I guess I am asking for a small lecture :)

bayareaguy 19y ago
I have a lot of scripts that sit on top of svn which I'm thinking of moving over to git. Even in the case of a single private repository git offers some advantages. Git seems a lot faster compared to svn, especially when checking out a large tree. svn co can be glacial at times. Also with git you don't have .svn directories all over the place. This may not seem like a big deal until you want to store a directory structure created by an application that wants total control over the directories it creates.
cstejerean 19y ago
git is great even if you're developing by yourself. I use git exclusively for all my work now (and use git-svn to integrate with others at work that use svn). Some of the benefits are: merge tracking: this will also come to subversion in the future (but you'll have to migrate your repository) having the entire repository checked out locally for offline use (being able to code on the train on the way to work is great) fast branches - branches are really fast, especially since they're done locally, and there's basically no excuse for not quickly creating a branch when you want to try something out, and merge tracking forking other open source repositories (including svn and cvs ones) for hacking and maintaing patches (until they get accepted upstream). git is nice and will attempt to always rebase your patches off the latest HEAD (and let you resolve conflicts if they occur). git bisect for binary searching for the revision that broke something (can do a binary search over revisions to find out which revision broke a certain test). did I mention that it integrates with svn? git svn clone http://svnrepo.com/trunk http://svnrepo.com/trunk # do stuff git add stuff/you/changed git commit git svn dcommit # commit changes from git into subversion I could go on...

by tx 19y ago

bayareaguy 19y ago

I have a lot of scripts that sit on top of svn which I'm thinking of moving over to git. Even in the case of a single private repository git offers some advantages. Git seems a lot faster compared to svn, especially when checking out a large tree. svn co can be glacial at times. Also with git you don't have .svn directories all over the place. This may not seem like a big deal until you want to store a directory structure created by an application that wants total control over the directories it creates.

cstejerean 19y ago

git is great even if you're developing by yourself. I use git exclusively for all my work now (and use git-svn to integrate with others at work that use svn). Some of the benefits are: merge tracking: this will also come to subversion in the future (but you'll have to migrate your repository) having the entire repository checked out locally for offline use (being able to code on the train on the way to work is great) fast branches - branches are really fast, especially since they're done locally, and there's basically no excuse for not quickly creating a branch when you want to try something out, and merge tracking forking other open source repositories (including svn and cvs ones) for hacking and maintaing patches (until they get accepted upstream). git is nice and will attempt to always rebase your patches off the latest HEAD (and let you resolve conflicts if they occur). git bisect for binary searching for the revision that broke something (can do a binary search over revisions to find out which revision broke a certain test). did I mention that it integrates with svn? git svn clone http://svnrepo.com/trunk http://svnrepo.com/trunk # do stuff git add stuff/you/changed git commit git svn dcommit # commit changes from git into subversion I could go on...