http://stevelosh.com/blog/2010/01/the-real-difference-betwee...
I feel strongly that `git checkout file` is correct though. What that operation is doing is taking something out of the DAG and putting it into the working tree. It's the same deal, the only difference is instead of pulling a tree object (associated with a commit) from the DAG into the working tree, you are instead pulling a glob. It makes intuitive sense to me that these two operations would be accessed through the same command. Furthermore, using the name 'revert' would make much less sense in the rather frequent case that you want to pull a blob from a commit that is not the current HEAD. Is it really "reverting" if I am pulling a file from a future commit in another branch into my working tree? I don't think naming commands after less powerful concepts is a good design decision.
No, they all want experience using Git. Do they actually need a distributed version control system? Probably not.
I am sure git is great for the complexities of developing the Linux kernel from remote locations, but most projects are not that. I would prefer something that is less distracting to the task in hand.
In my experience, many things were weird but just had to be learnt, submodules on the other hand, that's pretty crazy!
I sometimes feel like I'm the only one; I'm glad to hear that I'm not alone.