never seen this view before, it may seem confusing, but it shows the same concepts as a graphical viewer for Git history. We’re looking at the history of the README file, so the directory tree at top left When you install Git, you also get its visual tools, gitk and git-gui. gitk is a graphical history viewer. Think of it like a powerful GUI shell over git log and git grep. This is the tool to use when you’re reachable from any ref, not just HEAD. Gitk’s interface looks like this: Figure 177. The gitk history viewer On the top is something that looks a bit like the output of git log -- graph; each dot represents

never seen this view before, it may seem confusing, but it shows the same concepts as a graphical viewer for Git history. We’re looking at the history of the README file, so the directory tree at top left When you install Git, you also get its visual tools, gitk and git-gui. gitk is a graphical history viewer. Think of it like a powerful GUI shell over git log and git grep. This is the tool to use when you’re from any ref, not just HEAD. Gitk’s interface looks like this: 453 Figure 177. The gitk history viewer On the top is something that looks a bit like the output of git log --graph; each dot represents

never seen this view before, it may seem confusing, but it shows the same concepts as a graphical viewer for Git history. We’re looking at the history of the README file, so the directory tree at top left When you install Git, you also get its visual tools, gitk and git-gui. gitk is a graphical history viewer. Think of it like a powerful GUI shell over git log and git grep. This is the tool to use when you’re reachable from any ref, not just HEAD. Gitk’s interface looks like this: Figure 177. The gitk history viewer On the top is something that looks a bit like the output of git log -- graph; each dot represents