The Log Dialog retrieves all those log messages and shows them to you. Compare the selected revision with your working tree.
The default Diff-Tool is Tortoise Git Merge which is supplied with Tortoise Git.
For a deployment repo this is not a major issue, since the only commits should be ones already committed correctly before being pulled.
However, its sometimes useful to check that the commit markers (head,tags,remotes) look identical to the master repo.
It is harder to read than a visual file compare, but will show all file changes together in a compact format.
Compare the selected revision with the previous revision.
When you revert changes you may find that the operation takes a lot longer than you expect.From the Revision Log dialog select the revision of interest, then select If you want to see the changes of different branches (maybe the current one to another branch or two branches) you can use the log dialog and select the two revisions as described above for "Difference between two previous revisions".An easier way is to open the reference browser (cf. There you can click on one branch and select to see all changes between that branch and your current state of the working tree.Does not touch the index file nor the working tree at all (but resets the head to the selected commit, just like all modes do).This leaves all your changed files "Changes to be committed" as before. Any changes to tracked files in the working tree since the selected commit are discarded.Tortoise Git provides a built-in tool named from the context menu (cf. If you want to see the difference between the last committed revision and your working tree, assuming that the working tree hasn't been modified, just right click on the file. This will perform a diff between the revision before the last-commit-date (as recorded in your working tree) and the working BASE.