NAME git-log - Show commit logs SYNOPSIS git log [ ] [ ] [[--] ...] DESCRIPTION Shows the commit logs. List ... names, like the --decorate option of git-log (1) %D ref names witho…discussion about encoding in the git-log (1) manual page. --name-status Show only ... implies the -t option in git-log to also find trees. --pickaxe-all Whennames, like the --decorate option of git-log (1) %D ref names without the " (", ")" wrapping ... discussion about encoding in the git-log (1) manual page. --name-status Show onlydiscussion about encoding in the git-log (1) manual page. --name-status Show only ... implies the -t option in git-log to also find trees. --pickaxe-all Whendiscussion about encoding in the git-log (1) manual page. --name-status Show only ... implies the -t option in git-log to also find trees. --pickaxe-all Whendiscussion about encoding in the git-log (1) manual page. --name-status Show only ... implies the -t option in git-log to also find trees. --pickaxe-all Whenspecialized family of commit log tools: git-log (1), git-show (1), and git-whatchanged ... names, like the --decorate option of git-log (1) %D ref names without the " (", ")" wrapp…discussion of the --date option at git-log (1). blame.showEmail Show the author email instead ... always , git-diff (1), git-log (1), and git-show (1) will use colorPRETTY FORMATS" section of git-log (1).) Each pretty-printed commit will be rewrapped before ... Commit Formatting" section of git-log (1)). Useful with --group=format: . --group=…discussion about encoding in the git-log (1) manual page. --contents Annotate using the contents ... discussion of the --date option at git-log (1). --[no-]progress Progress stat…commits that would be excluded by git-log (1)'s --ancestry-path option will keep ... format string, as specified in git-log (1), to be used for the todo listdiscussion about encoding in the git-log (1) manual page. --contents Annotate using the contents ... discussion of the --date option at git-log (1). --[no-]progress Progress stat…git log program (see git-log (1)) that generates the patches. Compare the commits specified ... ALSO git-log (1) GIT Part of the git (1) suiteusers are encouraged to use git-log (1) instead. The whatchanged command is essentially ... same as git-log (1) but defaults to showing the raw format diff outputrepository or reinitialize an existing one. git-log (1) Show commit logs. git-maintenanceabbrev-commit --pretty=oneline ; see git-log (1) for more information. The "list" subcommand listsHEAD to examine the branch with git-log (1). The fetched objects will eventuallywhat is shown and how. See git-log (1). show [-u|--include-untracked|--only-untrackedcommit using "--pretty=reference" format (cf. git-log (1)). The revert.reference configuration variablethat you would give to the git-log (1) command. Here are more examples