4 ms·
"A big problem with git is that the commits-and-branching model is poorly thought through. It's very easy to find yourself on no branch at all, for instance, or
by jshen 16y ago
"A big problem with git is that the commits-and-branching model is poorly thought through. It's very easy to find yourself on no branch at all, for instance, or for a developer to believe they've committed work to a shared branch when in fact it's a private one (and therefore leave the rest of the team hanging.)"
I don't think you understand how git works. Calling it "poorly thought through" when you haven't taken the time to understand it is not a compelling argument.
"It's very easy to find yourself on no branch at all"
A branch is simply a pointer to a specific commit. If you checkout a random commit it is likely not a branch. I don't know why you find this troubling.
"It's very easy ... for a developer to believe they've committed work to a shared branch when in fact it's a private one"
Again, this is from a lack of understanding. All commits are to your local repository. It seems you haven't tried very hard to understand how git works.
- bokchoi 16y agoCalling it "poorly thought through" when you haven't taken the time to understand it is not a compelling argument. Neither is saying the OP hasn't taken the time to understand it.
- jshen 16y agoI don't understand what your saying. I said that the OP doesn't understand git basics, and that a critique based on a lack of understanding is not compelling. Are you suggesting that I'm wrong about his level of understanding or that one can make a valid critique of something they don't understand?
- bokchoi 16y agoI'm saying that perhaps his level of understanding is not to blame. Most responses to complaints about git are "you just don't understand." It is tiring.
- alinajaf 16y agoIt may be tiring, but it's still true. "[svn|rails|regex|whatever] is bad because I don't get it" is not an argument, just an expression of laziness/lack of interest.
- jshen 16y agoI went into barnes and noble one day and picked up the Pro Git book and sat in the cafe and read it for a few hours. After that I understood git fairly well and the things the OP said show that he hasn't put forth this minimal amount of effort. I don't think a few hours of study for a power tool is too much to ask, and I think it's reasonable to dismiss the arguments of someone who clearly hasn't put forth a sincere effort to understand it. Also, the book is available for free online http://progit.org/book/ http://progit.org/book/