News for hackers. Stuff that matters.
Re:Moving from SVN to Git in 1,000 easy steps by jlongster on Friday December 02, 2011 @02:59PM (#3305432)
It's saving you because you can freely commit without ever running into a conflict suprisingly.

Deal with the merges and conflicts when you want to. Also, it's lot faster to commit. You shouldn't be pushing out every commit -- just commit a lot and when you want others to see it, push it.

Re:Moving from SVN to Git in 1,000 easy steps by sixbrx on Friday December 02, 2011 @03:24PM (#3305536)
You can also freely branch and merge between your own private branches, without making everybody else see these numerous branches polluting the file hierarchy of the central repo.

More generally, I never liked how to cvs and subversion a branch is basically just a copy at the file level. That mixes version control metadata among the file paths that are themselves being version controlled.

Re:Moving from SVN to Git in 1,000 easy steps by gt384u on Friday December 02, 2011 @03:57PM (#3305643)
THIS. I worked at an organization with ~700 branches with names all pretty much meaningless for a single project, when maybe 10 were actually being developed on. Makes it almost impossible to understand the repo.
Re:Moving from SVN to Git in 1,000 easy steps by j_col on Friday December 02, 2011 @03:07PM (#3305455)
I could commit pretty freely using Subversion or Perforce to. As for the faster Git commits, is that just because you are only commiting locally? You still have the overhead of pushing to your central repo. Reading the original article, it seems his reason for switching to Git can be summed up in one word: Github.
Re:Moving from SVN to Git in 1,000 easy steps by jaggederest on Friday December 02, 2011 @04:14PM (#3305710)
> I could commit pretty freely using Subversion or Perforce to.

Pretty freely is not freely. That's like having 'decent' freedom of speech, y'see. Git allows you to commit any time, so fast you won't even notice the pause.

> As for the faster Git commits, is that just because you are only commiting locally? You still have the overhead of pushing to your central repo.

Yes, it's faster because it only commits locally. You should not push every commit to the central repo, and you should be committing more or less every time you change a file. Git allows you to be far more granular than SVN or perforce did.

It also allows you to throw things away and try things out without worrying about hurting someone else. Branching in SVN/Perforce is simply not worth the effort, but on Git, it's trivial.

Re:Moving from SVN to Git in 1,000 easy steps by brown9-2 on Friday December 02, 2011 @09:39PM (#3306719)
But in svn or p4 those commits are visible to everyone else immediately. With git they are only visible when you are ready to make them so - and you can amend or merge them into a single commit or slice them however you want beforehand.

Having your own private repo other than what is on the server allows you to experiment and make a lot more mistake without affecting others.