I am introducing git to a team of developers and i find gitk to be an amazing tool. It's also quite hard to understand, since understanding gitk requires an understanding of both git history and the viewer tool itself.
Does anyone have any good references to something like a "beginner's guide to git history with gitk" ?
What novices could really use in terms of "combination of gitk and history" is a specific explanation how to recognize what happened by looking at the gitk tree view.
As far as I got - the right way to look at the tree is (of course):
1. each node is a commit
2. ultimate parent is at the bottom
3. direct child to a commit is the one that happened first in the same branch (no matter who did it)
4. the node with 2 or more children indicates ... ?
5. merge commit node has 2 parents.
6. rebase is recognized ... ?
Screenshots would be appreciated as well.
The tree is actually representing the current state of the repository. What would be great is if we would be able to tell what happened by looking at the tree view.
Thanks
v.
The only thing I find useful about the gitk interface is the nice (colorful) branches overview..
If you want a gui for git, check TortoiseGit on windows or GitX on Mac or QGit on linux.