Thanks for the feedback! Regarding the setup, that could be an addition.
It probably need a clearer write up but I added the "Protocols" section to help people understand that SSH is not a must have; from what I've seen the Windows setup difficulties is mostly about SSH -- would you confirm that?
Interesting. Do you think that confusion comes from the fact that commit history (to not say 'time') is represented vertically (and sometime going upward and sometime downward)?
From my experience, most people issues with git is because they do not really understand how it works (or try to apply what they've seen with other cvs).
Now I agree that having to understand internals might be seen as an engineering failure, however
* internals are pretty quick to cover
* for students learning software development, I thought it would be interesting to see that you can have very few low-level objects that offer powerful high-level actions
Could you be a little more explicit about what you find too advanced or what specific points would need more explanations?
I intend to use this as a course material for git total beginners so your feedback is very important to me!
Agree that diagrams would help clarify some points. I was a bit short on time for this so I thought that only using git outputs could be enough; I will try to spend some time to incorporate some illustrations!