NAME git-rev-list - Lists commit objects in reverse chronological order SYNOPSIS git rev-list ... walk . Commit Formatting Using these options, git-rev-list (1) will act similarcommand takes options applicable to the git-rev-list (1) command to control what ... like the --date=human option of git-rev-list (1)) %cn committer name %cN committerlike the --date=human option of git-rev-list (1)) %cn committer name %cN committer ... like the --date=human option of git-rev-list (1)) %d ref names, likespecifications, see the --filter option in git-rev-list (1). --also-filter-submodules Also apply ... filter is provided (see --filter in git-rev-list (1)) and --recurse-submodules …like the --date=human option of git-rev-list (1)) %cn committer name %cN committer ... like the --date=human option of git-rev-list (1)) %d ref names, likeblobs) from the resulting packfile. See git-rev-list (1) for valid forms. --no-filter ... delta set to false. SEE ALSO git-rev-list (1) git-repack (1) git-prunetraversal is done by default, see git-rev-list (1) and its --no-walk optionpackfile containing all the objects. See git-rev-list (1) for valid forms. --filterredundant (1) Find redundant pack files. git-rev-list (1) Lists commit objects in reversevalues the --date option to git-rev-list (1) takes). If this formatting is providedfrom revs-file instead of calling git-rev-list (1). --reverse .. Walk history forward insteadancestor commit (via parent rewriting; see git-rev-list (1)). -M, -C Perform move and/orfilter is provided (see --filter in git-rev-list (1)) and --recurse-submodules is usedfrom revs-file instead of calling git-rev-list (1). --reverse .. Walk history forward insteadapplied to the submodule. See git-rev-list (1) for details on filter specificationsorigin/master). SEE ALSO git-rev-list (1), git-show-branch (1), git-merge (1) GITwalk option was specified, see git-rev-list (1). Note that specifying a range willancestor”. Remap to ancestor By using git-rev-list (1) arguments, e.g., path limiters