7. Git Tools
- 7.1 Revisions-Auswahl
- 7.2 Interactive Staging
- 7.3 Stashing and Cleaning
- 7.4 Ihre Arbeit signieren
- 7.5 Suchen
- 7.6 Rewriting History
- 7.7 Reset Demystified
- 7.8 Fortgeschrittenes Merging
- 7.9 Rerere
- 7.10 Debugging with Git
- 7.11 Submodules
- 7.12 Bundling
- 7.13 Replace
- 7.14 Anmeldeinformationen speichern
- 7.15 Zusammenfassung
10. Git Interna
- A3.1 Setup und Konfiguration
- A3.2 Projekte importieren und erstellen
- A3.3 Einfache Snapshot-Funktionen
- A3.4 Branching und Merging
- A3.5 Sharing and Updating Projects
- A3.6 Inspection and Comparison
- A3.7 Debugging
- A3.8 Patching
- A3.9 Email
- A3.10 External Systems
- A3.11 Administration
- A3.12 Plumbing Commands
A3.6 Appendix C: Git Kommandos - Inspection and Comparison
Inspection and Comparison
git show command can show a Git object in a simple and human readable way.
Normally you would use this to show the information about a tag or a commit.
We first use it to show annotated tag information in Annotierte Tags.
Later we use it quite a bit in Revisions-Auswahl to show the commits that our various revision selections resolve to.
One of the more interesting things we do with
git show is in Manual File Re-merging to extract specific file contents of various stages during a merge conflict.
git shortlog command is used to summarize the output of
It will take many of the same options that the
git log command will but instead of listing out all of the commits it will present a summary of the commits grouped by author.
We showed how to use it to create a nice changelog in Das Shortlog.
git describe command is used to take anything that resolves to a commit and produces a string that is somewhat human-readable and will not change.
It’s a way to get a description of a commit that is as unambiguous as a commit SHA-1 but more understandable.