6 ms·

In a centralized VCS check-ins and branching are the sorts of things that risk breaking tests and require your team's awareness Huh? Branching code in no way

In a centralized VCS check-ins and branching are the sorts of things that risk breaking tests and require your team's awareness Huh? Branching code in no way affects the code that has been branched. Instead of a flat directory as your sandbox you've got a full VCS at your disposal I don't get it. I can make as many branches in Subversion as I want. It's pretty common for me to have a couple of active branches off the same parent, as I try a couple of different approaches to a problem. So far, the only advantage I see to Git is the ability to make offline commits (presumably they sync when I have a network connection). But that's only an advantage in my hypothetical future where I'm developing code as I travel around the world.

wnight 15y ago
> Branching code in no way affects the code that has been branched. Usually it requires a repo admin - hence "team awareness". > So far, the only advantage I see to Git is the ability to make offline commits That's more important than you imagine. It also means nothing takes longer than a few seconds - branching, diffing, committing... > I don't get it. I can make as many branches in Subversion as I want. But you can't do it offline. You can't even check-in without the central server, let alone make and use branches, merge them, share them with another dev, etc. When you're offline you aren't using a VCS at all. > presumably they sync when I have a network connection Hah, no. That's half the fun.