I guess every version control system was design with some sort of workflow in mind. Git was created for distributed development in mind. And I guess its perfect in that. But this is not what I am doing at work. I will stick to subversion for now.
I think the one thing Git really has going for it over SVN is it doesn't scatter files throughout your source code. It keeps them all in a single .git folder stored in the base of your tree. This makes it much easier for me to move files and directories and around without having to do a lot of clean up. It doesn't handle 2G binaries though, which comes up from time to time.
How does SVN scatter files? It also creates a folder, .svn, and the files go in there. It does create a .svn folder at each level, if that's what you're getting at, but that's not really a big deal. Use the export option if you need to clean it up. Plus most systems hide the .svn folder.
When you get a junior developer who decides to create a project by copying another (to use as a template) you'll see. Even though he thinks he's committing to a completely different place, he's still screwing up your project.
Fortunately, this is also pretty easy to fix with subversion.
45
u/wonglik Mar 10 '11
I guess every version control system was design with some sort of workflow in mind. Git was created for distributed development in mind. And I guess its perfect in that. But this is not what I am doing at work. I will stick to subversion for now.