Show commit logs

--all
    Pretend as if all the refs in refs/ are listed on the command line as <commit>.

-M[<n>], --find-renames[=<n>]
    If generating diffs, detect and report renames for each commit. For following files across renames
    while traversing history, see --follow. If n is specified, it is a threshold on the similarity index
    (i.e. amount of addition/deletions compared to the file’s size). For example, -M90% means git should
    consider a delete/add pair to be a rename if more than 90% of the file hasn’t changed.

-C[<n>], --find-copies[=<n>]
    Detect copies as well as renames. See also --find-copies-harder. If n is specified, it has the same
    meaning as for -M<n>.

--numstat
    Similar to --stat, but shows number of added and deleted lines in decimal notation and pathname
    without abbreviation, to make it more machine friendly. For binary files, outputs two - instead of
    saying 0 0.

<since>..<until>
    Show only commits between the named two commits. When either <since> or <until> is omitted, it
    defaults to HEAD, i.e. the tip of the current branch. For a more complete list of ways to spell
    <since> and <until>, see gitrevisions(7).

[--] <path>...
    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.

    To prevent confusion with options and branch names, paths may need to be prefixed with "-- " to
    separate them from options or refnames.

--no-renames
    Turn off rename detection, even when the configuration file gives the default to do so.