git log [<options>] [<revision range>] [[--] <path>…]
Shows the commit logs.
The command takes options applicable to the git rev-list command to control what is shown and how, and options applicable to the git diff-* commands to control how the changes each commit introduces are shown.
Continue listing the history of a file beyond renames (works only for a single file).
Print out the ref names of any commits that are shown. If short is specified, the ref name prefixes refs/heads/, refs/tags/ and refs/remotes/ will not be printed. If full is specified, the full ref name (including prefix) will be printed. The default option is short.
Print out the ref name given on the command line by which each commit was reached.
Use mailmap file to map author and committer names and email to canonical real names and email addresses. See git-shortlog(1).
Without this flag, "git log -p <path>…" shows commits that touch the specified paths, and diffs about the same specified paths. With this, the full diff is shown for commits that touch the specified paths; this means that "<path>…" limits only commits, and doesn’t limit diff for those commits.
Note that this affects all diff-based output types, e.g. those produced by --stat etc.
Before the log message print out its size in bytes. Intended mainly for porcelain tools consumption. If Git is unable to produce a valid value size is set to zero. Note that only message is considered, if also a diff is shown its size is not included.
Show only commits in the specified revision range. When no
<revision range> is specified, it defaults to HEAD (i.e. the
whole history leading to the current commit). origin..HEAD
specifies all the commits reachable from the current commit
(i.e. HEAD), but not from origin. For a complete list of
ways to spell <revision range>, see the "Specifying Ranges"
section of gitrevisions(7).
Show only commits that are enough to explain how the files that match the specified paths came to be. See "History Simplification" below for details and other simplification modes.
Paths may need to be prefixed with "-- " to separate them from options or the revision range, when confusion arises.