> The problem I've had with Git is not that the basic model is hard to > understand -- it's that the basic model seems inadequate for many things, so > there's been a huge proliferation of mysterious switches that are poorly
Can you give an example when it's "not adequate"? For what it's worth -- there are typically only about five or six commands I use in git. Sure, there is tons of switches and commands out there, but I wouldn't read the docs of those switches without a special need (when you wish you could do something and don't know how). I suspect many people make the jump from CVS/SVN world and wish to repeat the same kind of workflow they had in the past. This is a mistake and it's not git-related. The workflow is going to be different, it's a different tool with different capabilities. If you transitioned to mercurial instead of git you'd face similar questions and problems. For example, one upside I see for people not familiar with git is that they can clone the repo, mess and experiment with git commands all they like and then invoke "gitk --all" and see whatever commits or merges they've made without them being pushed to the remote repository... Or, if you're not so sure about all this, you can fork the project on github, work on your own repo all you like and then simply file a pull request... even if you're a committer. Even if you tragically mess up... well, with git there is always a way to revert to a previous state -- it's not encouraged, but can be done. With SVN, once you mess up, it's there forever... Just to make it clear -- I had big doubts about the workflow when I first started using git... I think I can even say I was skeptical about the whole thing. But since then I learned to appreciate the differences of distributed revision control (be it mercurial or git) and I'd never, never want to go back to SVN. I don't qualify git as "better", but for my workflows it's definitely more convenient (and much, much faster). Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
