{ "content": [ { "type": "text", "text": "# git-rev-list (man)\n\n## NAME\n\ngit-rev-list - Lists commit objects in reverse chronological order\n\n## SYNOPSIS\n\ngit rev-list [] ... [[--] ...]\n\n## DESCRIPTION\n\nList commits that are reachable by following the parent links from the given commit(s), but\nexclude commits that are reachable from the one(s) given with a ^ in front of them. The\noutput is given in reverse chronological order by default.\n\n## TLDR\n\n> List revisions (commits) in reverse chronological order.\n\n- List all commits on the current branch:\n `git rev-list HEAD`\n- Print the latest commit that changed (add/edit/remove) a specific file on the current branch:\n `git rev-list {{-n|--max-count}} 1 HEAD -- {{path/to/file}}`\n- List commits more recent than a specific date, on a specific branch:\n `git rev-list --since \"{{2019-12-01 00:00:00}}\" {{branch_name}}`\n- List all merge commits on a specific commit:\n `git rev-list --merges {{commit}}`\n- Print the number of commits since a specific tag:\n `git rev-list {{tag_name}}..HEAD --count`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (81 subsections)\n- **PRETTY FORMATS**\n- **EXAMPLES**\n- **GIT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "git-rev-list", "section": "", "mode": "man", "summary": "git-rev-list - Lists commit objects in reverse chronological order", "synopsis": "git rev-list [] ... [[--] ...]", "tldr_summary": "List revisions (commits) in reverse chronological order.", "tldr_examples": [ { "description": "List all commits on the current branch", "command": "git rev-list HEAD" }, { "description": "Print the latest commit that changed (add/edit/remove) a specific file on the current branch", "command": "git rev-list {{-n|--max-count}} 1 HEAD -- {{path/to/file}}" }, { "description": "List commits more recent than a specific date, on a specific branch", "command": "git rev-list --since \"{{2019-12-01 00:00:00}}\" {{branch_name}}" }, { "description": "List all merge commits on a specific commit", "command": "git rev-list --merges {{commit}}" }, { "description": "Print the number of commits since a specific tag", "command": "git rev-list {{tag_name}}..HEAD --count" } ], "tldr_source": "official", "flags": [ { "flag": "", "long": "--all-match", "arg": null, "description": "Limit the commits output to ones that match all given --grep, instead of ones that match at least one." }, { "flag": "", "long": "--invert-grep", "arg": null, "description": "Limit the commits output to ones with log message that do not match the pattern specified with --grep=." }, { "flag": "-i", "long": "--regexp-ignore-case", "arg": null, "description": "Match the regular expression limiting patterns without regard to letter case." }, { "flag": "", "long": "--basic-regexp", "arg": null, "description": "Consider the limiting patterns to be basic regular expressions; this is the default." }, { "flag": "-E", "long": "--extended-regexp", "arg": null, "description": "Consider the limiting patterns to be extended regular expressions instead of the default basic regular expressions." }, { "flag": "-F", "long": "--fixed-strings", "arg": null, "description": "Consider the limiting patterns to be fixed strings (don’t interpret pattern as a regular expression)." }, { "flag": "-P", "long": "--perl-regexp", "arg": null, "description": "Consider the limiting patterns to be Perl-compatible regular expressions. Support for these types of regular expressions is an optional compile-time dependency. If Git wasn’t compiled with support for them providing this option will cause it to die." }, { "flag": "", "long": "--remove-empty", "arg": null, "description": "Stop when a given path disappears from the tree." }, { "flag": "", "long": "--merges", "arg": null, "description": "Print only merge commits. This is exactly the same as --min-parents=2." }, { "flag": "", "long": "--no-merges", "arg": null, "description": "Do not print commits with more than one parent. This is exactly the same as --max-parents=1. --min-parents=, --max-parents=, --no-min-parents, --no-max-parents Show only commits which have at least (or at most) that many parent commits. In particular, --max-parents=1 is the same as --no-merges, --min-parents=2 is the same as --merges. --max-parents=0 gives all root commits and --min-parents=3 all octopus merges. --no-min-parents and --no-max-parents reset these limits (to no limit) again. Equivalent forms are --min-parents=0 (any commit has 0 or more parents) and --max-parents=-1 (negative numbers denote no upper limit)." }, { "flag": "", "long": "--first-parent", "arg": null, "description": "Follow only the first parent commit upon seeing a merge commit. This option can give a better overview when viewing the evolution of a particular topic branch, because merges into a topic branch tend to be only about adjusting to updated upstream from time to time, and this option allows you to ignore the individual commits brought in to your history by such a merge." }, { "flag": "", "long": "--not", "arg": null, "description": "Reverses the meaning of the ^ prefix (or lack thereof) for all following revision specifiers, up to the next --not." }, { "flag": "", "long": "--all", "arg": null, "description": "Pretend as if all the refs in refs/, along with HEAD, are listed on the command line as . --branches[=] Pretend as if all the refs in refs/heads are listed on the command line as . If is given, limit branches to ones matching given shell glob. If pattern lacks ?, *, or [, /* at the end is implied. --tags[=] Pretend as if all the refs in refs/tags are listed on the command line as . If is given, limit tags to ones matching given shell glob. If pattern lacks ?, *, or [, /* at the end is implied. --remotes[=] Pretend as if all the refs in refs/remotes are listed on the command line as . If is given, limit remote-tracking branches to ones matching given shell glob. If pattern lacks ?, *, or [, /* at the end is implied. --glob= Pretend as if all the refs matching shell glob are listed on the command line as . Leading refs/, is automatically prepended if missing. If pattern lacks ?, *, or [, /* at the end is implied. --exclude= Do not include refs matching that the next --all, --branches, --tags, --remotes, or --glob would otherwise consider. Repetitions of this option accumulate exclusion patterns up to the next --all, --branches, --tags, --remotes, or --glob option (other options or arguments do not clear accumulated patterns). The patterns given should not begin with refs/heads, refs/tags, or refs/remotes when applied to --branches, --tags, or --remotes, respectively, and they must begin with refs/ when applied to --glob or --all. If a trailing /* is intended, it must be given explicitly." }, { "flag": "", "long": "--reflog", "arg": null, "description": "Pretend as if all objects mentioned by reflogs are listed on the command line as ." }, { "flag": "", "long": "--alternate-refs", "arg": null, "description": "Pretend as if all objects mentioned as ref tips of alternate repositories were listed on the command line. An alternate repository is any repository whose object directory is specified in objects/info/alternates. The set of included objects may be modified by core.alternateRefsCommand, etc. See git-config(1)." }, { "flag": "", "long": "--single-worktree", "arg": null, "description": "By default, all working trees will be examined by the following options when there are more than one (see git-worktree(1)): --all, --reflog and --indexed-objects. This option forces them to examine the current working tree only." }, { "flag": "", "long": "--ignore-missing", "arg": null, "description": "Upon seeing an invalid object name in the input, pretend as if the bad input was not given." }, { "flag": "", "long": "--stdin", "arg": null, "description": "In addition to the listed on the command line, read them from the standard input. If a -- separator is seen, stop reading commits and start reading paths to limit the result." }, { "flag": "", "long": "--quiet", "arg": null, "description": "Don’t print anything to standard output. This form is primarily meant to allow the caller to test the exit status to see if a range of objects is fully connected (or not). It is faster than redirecting stdout to /dev/null as the output does not have to be formatted." }, { "flag": "", "long": "--disk-usage", "arg": null, "description": "Suppress normal output; instead, print the sum of the bytes used for on-disk storage by the selected commits or objects. This is equivalent to piping the output into git cat-file --batch-check='%(objectsize:disk)', except that it runs much faster (especially with --use-bitmap-index). See the CAVEATS section in git-cat-file(1) for the limitations of what \"on-disk storage\" means." }, { "flag": "", "long": "--cherry-mark", "arg": null, "description": "Like --cherry-pick (see below) but mark equivalent commits with = rather than omitting them, and inequivalent ones with +." }, { "flag": "", "long": "--cherry-pick", "arg": null, "description": "Omit any commit that introduces the same change as another commit on the “other side” when the set of commits are limited with symmetric difference. For example, if you have two branches, A and B, a usual way to list all commits on only one side of them is with --left-right (see the example below in the description of the --left-right option). However, it shows the commits that were cherry-picked from the other branch (for example, “3rd on b” may be cherry-picked from branch A). With this option, such pairs of commits are excluded from the output." }, { "flag": "", "long": "--right-only", "arg": null, "description": "List only commits on the respective side of a symmetric difference, i.e. only those which would be marked < resp. > by --left-right. For example, --cherry-pick --right-only A...B omits those commits from B which are in A or are patch-equivalent to a commit in A. In other words, this lists the + commits from git cherry A B. More precisely, --cherry-pick --right-only --no-merges gives the exact list." }, { "flag": "", "long": "--cherry", "arg": null, "description": "A synonym for --right-only --cherry-mark --no-merges; useful to limit the output to the commits on our side and mark those that have been applied to the other side of a forked history with git log --cherry upstream...mybranch, similar to git cherry upstream mybranch." }, { "flag": "-g", "long": "--walk-reflogs", "arg": null, "description": "Instead of walking the commit ancestry chain, walk reflog entries from the most recent one to older ones. When this option is used you cannot specify commits to exclude (that is, ^commit, commit1..commit2, and commit1...commit2 notations cannot be used). With --pretty format other than oneline and reference (for obvious reasons), this causes the output to have two extra lines of information taken from the reflog. The reflog designator in the output may be shown as ref@{Nth} (where Nth is the reverse-chronological index in the reflog) or as ref@{timestamp} (with the timestamp for that entry), depending on a few rules: 1. If the starting point is specified as ref@{Nth}, show the index format. 2. If the starting point was specified as ref@{now}, show the timestamp format. 3. If neither was used, but --date was given on the command line, show the timestamp in the format requested by --date. 4. Otherwise, show the index format. Under --pretty=oneline, the commit message is prefixed with this information on the same line. This option cannot be combined with --reverse. See also git-reflog(1). Under --pretty=reference, this information will not be shown at all." }, { "flag": "", "long": "--merge", "arg": null, "description": "After a failed merge, show refs that touch files having a conflict and don’t exist on all heads to merge." }, { "flag": "", "long": "--boundary", "arg": null, "description": "Output excluded boundary commits. Boundary commits are prefixed with -." }, { "flag": "", "long": "--use-bitmap-index", "arg": null, "description": "Try to speed up the traversal using the pack bitmap index (if one is available). Note that when traversing with --objects, trees and blobs will not have their associated path printed. --progress=
Show progress reports on stderr as objects are considered. The
text will be printed with each progress update." }, { "flag": "", "long": "--simplify-by-decoration", "arg": null, "description": "Commits that are referred by some branch or tag are selected. Note that extra commits can be shown to give a meaningful history. The following options affect the way the simplification is performed: Default mode Simplifies the history to the simplest history explaining the final state of the tree. Simplest because it prunes some side branches if the end result is the same (i.e. merging branches with the same content)" }, { "flag": "", "long": "--show-pulls", "arg": null, "description": "Include all commits from the default mode, but also any merge commits that are not TREESAME to the first parent but are TREESAME to a later parent. This mode is helpful for showing the merge commits that \"first introduced\" a change to a branch." }, { "flag": "", "long": "--full-history", "arg": null, "description": "Same as the default mode, but does not prune some history." }, { "flag": "", "long": "--dense", "arg": null, "description": "Only the selected commits are shown, plus some to have a meaningful history." }, { "flag": "", "long": "--sparse", "arg": null, "description": "All commits in the simplified history are shown." }, { "flag": "", "long": "--simplify-merges", "arg": null, "description": "Additional option to --full-history to remove some needless merges from the resulting history, as there are no selected commits contributing to this merge." }, { "flag": "", "long": "--ancestry-path", "arg": null, "description": "When given a range of commits to display (e.g. commit1..commit2 or commit2 ^commit1), only display commits that exist directly on the ancestry chain between the commit1 and commit2, i.e. commits that are both descendants of commit1, and ancestors of commit2. A more detailed explanation follows. Suppose you specified foo as the . We shall call commits that modify foo !TREESAME, and the rest TREESAME. (In a diff filtered for foo, they look different and equal, respectively.) In the following, we will always refer to the same example history to illustrate the differences between simplification settings. We assume that you are filtering for a file foo in this commit graph: .-A---M---N---O---P---Q / / / / / / I B C D E Y \\ / / / / / `-------------' X The horizontal line of history A---Q is taken to be the first parent of each merge. The commits are: • I is the initial commit, in which foo exists with contents “asdf”, and a file quux exists with contents “quux”. Initial commits are compared to an empty tree, so I is !TREESAME. • In A, foo contains just “foo”. • B contains the same change as A. Its merge M is trivial and hence TREESAME to all parents. • C does not change foo, but its merge N changes it to “foobar”, so it is not TREESAME to any parent. • D sets foo to “baz”. Its merge O combines the strings from N and D to “foobarbaz”; i.e., it is not TREESAME to any parent. • E changes quux to “xyzzy”, and its merge P combines the strings to “quux xyzzy”. P is TREESAME to O, but not to E. • X is an independent root commit that added a new file side, and Y modified it. Y is TREESAME to X. Its merge Q added side to P, and Q is TREESAME to P, but not to Y. rev-list walks backwards through history, including or excluding commits based on whether --full-history and/or parent rewriting (via --parents or --children) are used. The following settings are available. Default mode Commits are included if they are not TREESAME to any parent (though this can be changed, see --sparse below). If the commit was a merge, and it was TREESAME to one parent, follow only that parent. (Even if there are several TREESAME parents, follow only one of them.) Otherwise, follow all parents. This results in: .-A---N---O / / / I---------D Note how the rule to only follow the TREESAME parent, if one is available, removed B from consideration entirely. C was considered via N, but is TREESAME. Root commits are compared to an empty tree, so I is !TREESAME. Parent/child relations are only visible with --parents, but that does not affect the commits selected in default mode, so we have shown the parent lines. --full-history without parent rewriting This mode differs from the default in one point: always follow all parents of a merge, even if it is TREESAME to one of them. Even if more than one side of the merge has commits that are included, this does not imply that the merge itself is! In the example, we get I A B N D O P Q M was excluded because it is TREESAME to both parents. E, C and B were all walked, but only B was !TREESAME, so the others do not appear. Note that without parent rewriting, it is not really possible to talk about the parent/child relationships between the commits, so we show them disconnected. --full-history with parent rewriting Ordinary commits are only included if they are !TREESAME (though this can be changed, see --sparse below). Merges are always included. However, their parent list is rewritten: Along each parent, prune away commits that are not included themselves. This results in .-A---M---N---O---P---Q / / / / / I B / D / \\ / / / / `-------------' Compare to --full-history without rewriting above. Note that E was pruned away because it is TREESAME, but the parent list of P was rewritten to contain E's parent I. The same happened for C and N, and X, Y and Q. In addition to the above settings, you can change whether TREESAME affects inclusion:" }, { "flag": "", "long": "--dense", "arg": null, "description": "Commits that are walked are included if they are not TREESAME to any parent." }, { "flag": "", "long": "--sparse", "arg": null, "description": "All commits that are walked are included. Note that without --full-history, this still simplifies merges: if one of the parents is TREESAME, we follow only that one, so the other sides of the merge are never walked." }, { "flag": "", "long": "--simplify-merges", "arg": null, "description": "First, build a history graph in the same way that --full-history with parent rewriting does (see above). Then simplify each commit C to its replacement C' in the final history according to the following rules: • Set C' to C. • Replace each parent P of C' with its simplification P'. In the process, drop parents that are ancestors of other parents or that are root commits TREESAME to an empty tree, and remove duplicates, but take care to never drop all parents that we are TREESAME to. • If after this parent rewriting, C' is a root or merge commit (has zero or >1 parents), a boundary commit, or !TREESAME, it remains. Otherwise, it is replaced with its only parent. The effect of this is best shown by way of comparing to --full-history with parent rewriting. The example turns into: .-A---M---N---O / / / I B D \\ / / `---------' Note the major differences in N, P, and Q over --full-history: • N's parent list had I removed, because it is an ancestor of the other parent M. Still, N remained because it is !TREESAME. • P's parent list similarly had I removed. P was then removed completely, because it had one parent and is TREESAME. • Q's parent list had Y simplified to X. X was then removed, because it was a TREESAME root. Q was then removed completely, because it had one parent and is TREESAME. There is another simplification mode available:" }, { "flag": "", "long": "--ancestry-path", "arg": null, "description": "Limit the displayed commits to those directly on the ancestry chain between the “from” and “to” commits in the given commit range. I.e. only display commits that are ancestor of the “to” commit and descendants of the “from” commit. As an example use case, consider the following commit history: D---E-------F / \\ \\ B---C---G---H---I---J / \\ A-------K---------------L--M A regular D..M computes the set of commits that are ancestors of M, but excludes the ones that are ancestors of D. This is useful to see what happened to the history leading to M since D, in the sense that “what does M have that did not exist in D”. The result in this example would be all the commits, except A and B (and D itself, of course). When we want to find out what commits in M are contaminated with the bug introduced by D and need fixing, however, we might want to view only the subset of D..M that are actually descendants of D, i.e. excluding C and K. This is exactly what the --ancestry-path option does. Applied to the D..M range, it results in: E-------F \\ \\ G---H---I---J \\ L--M Before discussing another option, --show-pulls, we need to create a new example history. A common problem users face when looking at simplified history is that a commit they know changed a file somehow does not appear in the file’s simplified history. Let’s demonstrate a new example and show how options such as --full-history and --simplify-merges works in that case: .-A---M-----C--N---O---P / / \\ \\ \\/ / / I B \\ R-'`-Z' / \\ / \\/ / \\ / /\\ / `---X--' `---Y--' For this example, suppose I created file.txt which was modified by A, B, and X in different ways. The single-parent commits C, Z, and Y do not change file.txt. The merge commit M was created by resolving the merge conflict to include both changes from A and B and hence is not TREESAME to either. The merge commit R, however, was created by ignoring the contents of file.txt at M and taking only the contents of file.txt at X. Hence, R is TREESAME to X but not M. Finally, the natural merge resolution to create N is to take the contents of file.txt at R, so N is TREESAME to R but not C. The merge commits O and P are TREESAME to their first parents, but not to their second parents, Z and Y respectively. When using the default mode, N and R both have a TREESAME parent, so those edges are walked and the others are ignored. The resulting history graph is: I---X When using --full-history, Git walks every edge. This will discover the commits A and B and the merge M, but also will reveal the merge commits O and P. With parent rewriting, the resulting graph is: .-A---M--------N---O---P / / \\ \\ \\/ / / I B \\ R-'`--' / \\ / \\/ / \\ / /\\ / `---X--' `------' Here, the merge commits O and P contribute extra noise, as they did not actually contribute a change to file.txt. They only merged a topic that was based on an older version of file.txt. This is a common issue in repositories using a workflow where many contributors work in parallel and merge their topic branches along a single trunk: manu unrelated merges appear in the --full-history results. When using the --simplify-merges option, the commits O and P disappear from the results. This is because the rewritten second parents of O and P are reachable from their first parents. Those edges are removed and then the commits look like single-parent commits that are TREESAME to their parent. This also happens to the commit N, resulting in a history view as follows: .-A---M--. / / \\ I B R \\ / / \\ / / `---X--' In this view, we see all of the important single-parent changes from A, B, and X. We also see the carefully-resolved merge M and the not-so-carefully-resolved merge R. This is usually enough information to determine why the commits A and B \"disappeared\" from history in the default view. However, there are a few issues with this approach. The first issue is performance. Unlike any previous option, the --simplify-merges option requires walking the entire commit history before returning a single result. This can make the option difficult to use for very large repositories. The second issue is one of auditing. When many contributors are working on the same repository, it is important which merge commits introduced a change into an important branch. The problematic merge R above is not likely to be the merge commit that was used to merge into an important branch. Instead, the merge N was used to merge R and X into the important branch. This commit may have information about why the change X came to override the changes from A and B in its commit message." }, { "flag": "", "long": "--show-pulls", "arg": null, "description": "In addition to the commits shown in the default history, show each merge commit that is not TREESAME to its first parent but is TREESAME to a later parent. When a merge commit is included by --show-pulls, the merge is treated as if it \"pulled\" the change from another branch. When using --show-pulls on this example (and no other options) the resulting graph is: I---X---R---N Here, the merge commits R and N are included because they pulled the commits X and R into the base branch, respectively. These merges are the reason the commits A and B do not appear in the default history. When --show-pulls is paired with --simplify-merges, the graph includes all of the necessary information: .-A---M--. N / / \\ / I B R \\ / / \\ / / `---X--' Notice that since M is reachable from R, the edge from N to M was simplified away. However, N still appears in the history as an important commit because it \"pulled\" the change R into the main branch. The --simplify-by-decoration option allows you to view only the big picture of the topology of the history, by omitting commits that are not referenced by tags. Commits are marked as !TREESAME (in other words, kept after history simplification rules described above) if (1) they are referenced by tags, or (2) they change the contents of the paths given on the command line. All other commits are marked as TREESAME (subject to be simplified away)." }, { "flag": "", "long": "--bisect", "arg": null, "description": "Limit output to the one commit object which is roughly halfway between included and excluded commits. Note that the bad bisection ref refs/bisect/bad is added to the included commits (if it exists) and the good bisection refs refs/bisect/good-* are added to the excluded commits (if they exist). Thus, supposing there are no refs in refs/bisect/, if $ git rev-list --bisect foo ^bar ^baz outputs midpoint, the output of the two commands $ git rev-list foo ^midpoint $ git rev-list midpoint ^bar ^baz would be of roughly the same length. Finding the change which introduces a regression is thus reduced to a binary search: repeatedly generate and test new 'midpoint’s until the commit chain is of length one." }, { "flag": "", "long": "--bisect-vars", "arg": null, "description": "This calculates the same as --bisect, except that refs in refs/bisect/ are not used, and except that this outputs text ready to be eval’ed by the shell. These lines will assign the name of the midpoint revision to the variable bisectrev, and the expected number of commits to be tested after bisectrev is tested to bisectnr, the expected number of commits to be tested if bisectrev turns out to be good to bisectgood, the expected number of commits to be tested if bisectrev turns out to be bad to bisectbad, and the number of commits we are bisecting right now to bisectall." }, { "flag": "", "long": "--bisect-all", "arg": null, "description": "This outputs all the commit objects between the included and excluded commits, ordered by their distance to the included and excluded commits. Refs in refs/bisect/ are not used. The farthest from them is displayed first. (This is the only one displayed by --bisect.) This is useful because it makes it easy to choose a good commit to test when you want to avoid to test some of them for some reason (they may not compile for example). This option can be used along with --bisect-vars, in this case, after all the sorted commit objects, there will be the same text as if --bisect-vars had been used alone." }, { "flag": "", "long": "--date-order", "arg": null, "description": "Show no parents before all of its children are shown, but otherwise show commits in the commit timestamp order." }, { "flag": "", "long": "--author-date-order", "arg": null, "description": "Show no parents before all of its children are shown, but otherwise show commits in the author timestamp order." }, { "flag": "", "long": "--topo-order", "arg": null, "description": "Show no parents before all of its children are shown, and avoid showing commits on multiple lines of history intermixed. For example, in a commit history like this: ---1----2----4----7 \\ \\ 3----5----6----8--- where the numbers denote the order of commit timestamps, git rev-list and friends with --date-order show the commits in the timestamp order: 8 7 6 5 4 3 2 1. With --topo-order, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5 3 1); some older commits are shown before newer ones in order to avoid showing the commits from two parallel development track mixed together." }, { "flag": "", "long": "--reverse", "arg": null, "description": "Output the commits chosen to be shown (see Commit Limiting section above) in reverse order. Cannot be combined with --walk-reflogs." }, { "flag": "", "long": "--objects", "arg": null, "description": "Print the object IDs of any object referenced by the listed commits. --objects foo ^bar thus means “send me all object IDs which I need to download if I have the commit object bar but not foo”." }, { "flag": "", "long": "--in-commit-order", "arg": null, "description": "Print tree and blob ids in order of the commits. The tree and blob ids are printed after they are first referenced by a commit." }, { "flag": "", "long": "--objects-edge", "arg": null, "description": "Similar to --objects, but also print the IDs of excluded commits prefixed with a “-” character. This is used by git-pack-objects(1) to build a “thin” pack, which records objects in deltified form based on objects contained in these excluded commits to reduce network traffic." }, { "flag": "", "long": "--objects-edge-aggressive", "arg": null, "description": "Similar to --objects-edge, but it tries harder to find excluded commits at the cost of increased time. This is used instead of --objects-edge to build “thin” packs for shallow repositories." }, { "flag": "", "long": "--indexed-objects", "arg": null, "description": "Pretend as if all trees and blobs used by the index are listed on the command line. Note that you probably want to use --objects, too." }, { "flag": "", "long": "--unpacked", "arg": null, "description": "Only useful with --objects; print the object IDs that are not in packs." }, { "flag": "", "long": "--object-names", "arg": null, "description": "Only useful with --objects; print the names of the object IDs that are found. This is the default behavior." }, { "flag": "", "long": "--no-object-names", "arg": null, "description": "Only useful with --objects; does not print the names of the object IDs that are found. This inverts --object-names. This flag allows the output to be more easily parsed by commands such as git-cat-file(1). --filter= Only useful with one of the --objects*; omits objects (usually blobs) from the list of printed objects. The may be one of the following: The form --filter=blob:none omits all blobs. The form --filter=blob:limit=[kmg] omits blobs larger than n bytes or units. n may be zero. The suffixes k, m, and g can be used to name units in KiB, MiB, or GiB. For example, blob:limit=1k is the same as blob:limit=1024. The form --filter=object:type=(tag|commit|tree|blob) omits all objects which are not of the requested type. The form --filter=sparse:oid= uses a sparse-checkout specification contained in the blob (or blob-expression) to omit blobs that would not be required for a sparse checkout on the requested refs. The form --filter=tree: omits all blobs and trees whose depth from the root tree is >= (minimum depth if an object is located at multiple depths in the commits traversed). =0 will not include any trees or blobs unless included explicitly in the command-line (or standard input when --stdin is used). =1 will include only the tree and blobs which are referenced directly by a commit reachable from or an explicitly-given object. =2 is like =1 while also including trees and blobs one more level removed from an explicitly-given commit or tree. Note that the form --filter=sparse:path= that wants to read from an arbitrary path on the filesystem has been dropped for security reasons. Multiple --filter= flags can be specified to combine filters. Only objects which are accepted by every filter are included. The form --filter=combine:++... can also be used to combined several filters, but this is harder than just repeating the --filter flag and is usually not necessary. Filters are joined by + and individual filters are %-encoded (i.e. URL-encoded). Besides the + and % characters, the following characters are reserved and also must be encoded: ~!@#$^&*()[]{}\\;\",<>?'` as well as all characters with ASCII code <= 0x20, which includes space and newline. Other arbitrary characters can also be encoded. For instance, combine:tree:3+blob:none and combine:tree%3A3+blob%3Anone are equivalent." }, { "flag": "", "long": "--no-filter", "arg": null, "description": "Turn off any previous --filter= argument." }, { "flag": "", "long": "--filter-provided-objects", "arg": null, "description": "Filter the list of explicitly provided objects, which would otherwise always be printed even if they did not match any of the filters. Only useful with --filter=." }, { "flag": "", "long": "--filter-print-omitted", "arg": null, "description": "Only useful with --filter=; prints a list of the objects omitted by the filter. Object IDs are prefixed with a “~” character. --missing= A debug option to help with future \"partial clone\" development. This option specifies how missing objects are handled. The form --missing=error requests that rev-list stop with an error if a missing object is encountered. This is the default action. The form --missing=allow-any will allow object traversal to continue if a missing object is encountered. Missing objects will silently be omitted from the results. The form --missing=allow-promisor is like allow-any, but will only allow object traversal to continue for EXPECTED promisor missing objects. Unexpected missing objects will raise an error. The form --missing=print is like allow-any, but will also print a list of the missing objects. Object IDs are prefixed with a “?” character." }, { "flag": "", "long": "--exclude-promisor-objects", "arg": null, "description": "(For internal use only.) Prefilter object traversal at promisor boundary. This is used with partial clone. This is stronger than --missing=allow-promisor because it limits the traversal, rather than just silencing errors about missing objects." }, { "flag": "", "long": null, "arg": null, "description": "Only show the given commits, but do not traverse their ancestors. This has no effect if a range is specified. If the argument unsorted is given, the commits are shown in the order they were given on the command line. Otherwise (if sorted or no argument was given), the commits are shown in reverse chronological order by commit time. Cannot be combined with --graph." }, { "flag": "", "long": "--do-walk", "arg": null, "description": "Overrides a previous --no-walk." }, { "flag": "", "long": "--abbrev-commit", "arg": null, "description": "Instead of showing the full 40-byte hexadecimal commit object name, show a prefix that names the object uniquely. \"--abbrev=\" (which also modifies diff output, if it is displayed) option can be used to specify the minimum length of the prefix. This should make \"--pretty=oneline\" a whole lot more readable for people using 80-column terminals." }, { "flag": "", "long": "--no-abbrev-commit", "arg": null, "description": "Show the full 40-byte hexadecimal commit object name. This negates --abbrev-commit, either explicit or implied by other options such as \"--oneline\". It also overrides the log.abbrevCommit variable." }, { "flag": "", "long": "--oneline", "arg": null, "description": "This is a shorthand for \"--pretty=oneline --abbrev-commit\" used together. --encoding= Commit objects record the character encoding used for the log message in their encoding header; this option can be used to tell the command to re-code the commit log message in the encoding preferred by the user. For non plumbing commands this defaults to UTF-8. Note that if an object claims to be encoded in X and we are outputting in X, we will output the object verbatim; this means that invalid sequences in the original commit may be copied to the output. Likewise, if iconv(3) fails to convert the commit, we will quietly output the original object verbatim. --expand-tabs=, --expand-tabs, --no-expand-tabs Perform a tab expansion (replace each tab with enough spaces to fill to the next display column that is multiple of ) in the log message before showing it in the output. --expand-tabs is a short-hand for --expand-tabs=8, and --no-expand-tabs is a short-hand for --expand-tabs=0, which disables tab expansion. By default, tabs are expanded in pretty formats that indent the log message by 4 spaces (i.e. medium, which is the default, full, and fuller)." }, { "flag": "", "long": "--show-signature", "arg": null, "description": "Check the validity of a signed commit object by passing the signature to gpg --verify and show the output." }, { "flag": "", "long": "--relative-date", "arg": null, "description": "Synonym for --date=relative. --date= Only takes effect for dates shown in human-readable format, such as when using --pretty. log.date config variable sets a default value for the log command’s --date option. By default, dates are shown in the original time zone (either committer’s or author’s). If -local is appended to the format (e.g., iso-local), the user’s local time zone is used instead. --date=relative shows dates relative to the current time, e.g. “2 hours ago”. The -local option has no effect for --date=relative. --date=local is an alias for --date=default-local. --date=iso (or --date=iso8601) shows timestamps in a ISO 8601-like format. The differences to the strict ISO 8601 format are: • a space instead of the T date/time delimiter • a space between time and time zone • no colon between hours and minutes of the time zone --date=iso-strict (or --date=iso8601-strict) shows timestamps in strict ISO 8601 format. --date=rfc (or --date=rfc2822) shows timestamps in RFC 2822 format, often found in email messages. --date=short shows only the date, but not the time, in YYYY-MM-DD format. --date=raw shows the date as seconds since the epoch (1970-01-01 00:00:00 UTC), followed by a space, and then the timezone as an offset from UTC (a + or - with four digits; the first two are hours, and the second two are minutes). I.e., as if the timestamp were formatted with strftime(\"%s %z\")). Note that the -local option does not affect the seconds-since-epoch value (which is always measured in UTC), but does switch the accompanying timezone value. --date=human shows the timezone if the timezone does not match the current time-zone, and doesn’t print the whole date if that matches (ie skip printing year for dates that are \"this year\", but also skip the whole date itself if it’s in the last few days and we can just say what weekday it was). For older dates the hour and minute is also omitted. --date=unix shows the date as a Unix epoch timestamp (seconds since 1970). As with --raw, this is always in UTC and therefore -local has no effect. --date=format:... feeds the format ... to your system strftime, except for %z and %Z, which are handled internally. Use --date=format:%c to show the date in your system locale’s preferred format. See the strftime manual for a complete list of format placeholders. When using -local, the correct syntax is --date=format-local:.... --date=default is the default format, and is similar to --date=rfc2822, with a few exceptions: • there is no comma after the day-of-week • the time zone is omitted when the local time zone is used" }, { "flag": "", "long": "--header", "arg": null, "description": "Print the contents of the commit in raw-format; each record is separated with a NUL character." }, { "flag": "", "long": "--no-commit-header", "arg": null, "description": "Suppress the header line containing \"commit\" and the object ID printed before the specified format. This has no effect on the built-in formats; only custom formats are affected." }, { "flag": "", "long": "--commit-header", "arg": null, "description": "Overrides a previous --no-commit-header." }, { "flag": "", "long": "--parents", "arg": null, "description": "Print also the parents of the commit (in the form \"commit parent...\"). Also enables parent rewriting, see History Simplification above." }, { "flag": "", "long": "--children", "arg": null, "description": "Print also the children of the commit (in the form \"commit child...\"). Also enables parent rewriting, see History Simplification above." }, { "flag": "", "long": "--timestamp", "arg": null, "description": "Print the raw commit timestamp." }, { "flag": "", "long": "--left-right", "arg": null, "description": "Mark which side of a symmetric difference a commit is reachable from. Commits from the left side are prefixed with < and those from the right with >. If combined with --boundary, those commits are prefixed with -. For example, if you have this topology: y---b---b branch B / \\ / / . / / \\ o---x---a---a branch A you would get an output like this: $ git rev-list --left-right --boundary --pretty=oneline A...B >bbbbbbb... 3rd on b >bbbbbbb... 2nd on b ] When --graph is not used, all history branches are flattened which can make it hard to see that the two consecutive commits do not belong to a linear branch. This option puts a barrier in between them in that case. If is specified, it is the string that will be shown instead of the default one." }, { "flag": "", "long": "--count", "arg": null, "description": "Print a number stating how many commits would have been listed, and suppress all other output. When used together with --left-right, instead print the counts for left and right commits, separated by a tab. When used together with --cherry-mark, omit patch equivalent commits from these counts and print the count for equivalent commits separated by a tab." } ], "examples": [ "• Print the list of commits reachable from the current branch.", "git rev-list HEAD", "• Print the list of commits on this branch, but not present in the upstream branch.", "git rev-list @{upstream}..HEAD", "• Format commits with their author and commit message (see also the porcelain git-log(1)).", "git rev-list --format=medium HEAD", "• Format commits along with their diffs (see also the porcelain git-log(1), which can do", "this in a single process).", "git rev-list HEAD |", "git diff-tree --stdin --format=medium -p", "• Print the list of commits on the current branch that touched any file in the", "Documentation directory.", "git rev-list HEAD -- Documentation/", "• Print the list of commits authored by you in the past year, on any branch, tag, or other", "ref.", "git rev-list --author=you@example.com --since=1.year.ago --all", "• Print the list of objects reachable from the current branch (i.e., all commits and the", "blobs and trees they contain).", "git rev-list --objects HEAD", "• Compare the disk size of all reachable objects, versus those reachable from reflogs,", "versus the total packed size. This can tell you whether running git repack -ad might", "reduce the repository size (by dropping unreachable objects), and whether expiring", "reflogs might help.", "# reachable objects", "git rev-list --disk-usage --objects --all", "# plus reflogs", "git rev-list --disk-usage --objects --all --reflog", "# total disk size used", "du -c .git/objects/pack/*.pack .git/objects/??/*", "# alternative to du: add up \"size\" and \"size-pack\" fields", "git count-objects -v", "• Report the disk size of each branch, not including objects used by the current branch.", "This can find outliers that are contributing to a bloated repository size (e.g., because", "somebody accidentally committed large build artifacts).", "git for-each-ref --format='%(refname)' |", "while read branch", "do", "size=$(git rev-list --disk-usage --objects HEAD..$branch)", "echo \"$size $branch\"", "done |", "sort -n", "• Compare the on-disk size of branches in one group of refs, excluding another. If you", "co-mingle objects from multiple remotes in a single repository, this can show which", "remotes are contributing to the repository size (taking the size of origin as a", "baseline).", "git rev-list --disk-usage --objects --remotes=$suspect --not --remotes=origin" ], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 3, "subsections": [] }, { "name": "DESCRIPTION", "lines": 35, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "Commit Limiting", "lines": 41 }, { "name": "--all-match", "lines": 3, "long": "--all-match" }, { "name": "--invert-grep", "lines": 3, "long": "--invert-grep" }, { "name": "-i, --regexp-ignore-case", "lines": 2, "flag": "-i", "long": "--regexp-ignore-case" }, { "name": "--basic-regexp", "lines": 2, "long": "--basic-regexp" }, { "name": "-E, --extended-regexp", "lines": 3, "flag": "-E", "long": "--extended-regexp" }, { "name": "-F, --fixed-strings", "lines": 3, "flag": "-F", "long": "--fixed-strings" }, { "name": "-P, --perl-regexp", "lines": 5, "flag": "-P", "long": "--perl-regexp" }, { "name": "--remove-empty", "lines": 2, "long": "--remove-empty" }, { "name": "--merges", "lines": 2, "long": "--merges" }, { "name": "--no-merges", "lines": 12, "long": "--no-merges" }, { "name": "--first-parent", "lines": 6, "long": "--first-parent" }, { "name": "--not", "lines": 3, "long": "--not" }, { "name": "--all", "lines": 34, "long": "--all" }, { "name": "--reflog", "lines": 3, "long": "--reflog" }, { "name": "--alternate-refs", "lines": 5, "long": "--alternate-refs" }, { "name": "--single-worktree", "lines": 4, "long": "--single-worktree" }, { "name": "--ignore-missing", "lines": 3, "long": "--ignore-missing" }, { "name": "--stdin", "lines": 4, "long": "--stdin" }, { "name": "--quiet", "lines": 4, "long": "--quiet" }, { "name": "--disk-usage", "lines": 6, "long": "--disk-usage" }, { "name": "--cherry-mark", "lines": 3, "long": "--cherry-mark" }, { "name": "--cherry-pick", "lines": 9, "long": "--cherry-pick" }, { "name": "--left-only, --right-only", "lines": 8, "long": "--right-only" }, { "name": "--cherry", "lines": 5, "long": "--cherry" }, { "name": "-g, --walk-reflogs", "lines": 24, "flag": "-g", "long": "--walk-reflogs" }, { "name": "--merge", "lines": 3, "long": "--merge" }, { "name": "--boundary", "lines": 2, "long": "--boundary" }, { "name": "--use-bitmap-index", "lines": 8, "long": "--use-bitmap-index" }, { "name": "History Simplification", "lines": 10 }, { "name": "--simplify-by-decoration", "lines": 11, "long": "--simplify-by-decoration" }, { "name": "--show-pulls", "lines": 4, "long": "--show-pulls" }, { "name": "--full-history", "lines": 2, "long": "--full-history" }, { "name": "--dense", "lines": 2, "long": "--dense" }, { "name": "--sparse", "lines": 2, "long": "--sparse" }, { "name": "--simplify-merges", "lines": 3, "long": "--simplify-merges" }, { "name": "--ancestry-path", "lines": 100, "long": "--ancestry-path" }, { "name": "--dense", "lines": 2, "long": "--dense" }, { "name": "--sparse", "lines": 5, "long": "--sparse" }, { "name": "--simplify-merges", "lines": 39, "long": "--simplify-merges" }, { "name": "--ancestry-path", "lines": 107, "long": "--ancestry-path" }, { "name": "--show-pulls", "lines": 33, "long": "--show-pulls" }, { "name": "Bisection Helpers", "lines": 1 }, { "name": "--bisect", "lines": 17, "long": "--bisect" }, { "name": "--bisect-vars", "lines": 8, "long": "--bisect-vars" }, { "name": "--bisect-all", "lines": 10, "long": "--bisect-all" }, { "name": "Commit Ordering", "lines": 2 }, { "name": "--date-order", "lines": 3, "long": "--date-order" }, { "name": "--author-date-order", "lines": 3, "long": "--author-date-order" }, { "name": "--topo-order", "lines": 16, "long": "--topo-order" }, { "name": "--reverse", "lines": 3, "long": "--reverse" }, { "name": "Object Traversal", "lines": 2 }, { "name": "--objects", "lines": 4, "long": "--objects" }, { "name": "--in-commit-order", "lines": 3, "long": "--in-commit-order" }, { "name": "--objects-edge", "lines": 5, "long": "--objects-edge" }, { "name": "--objects-edge-aggressive", "lines": 4, "long": "--objects-edge-aggressive" }, { "name": "--indexed-objects", "lines": 3, "long": "--indexed-objects" }, { "name": "--unpacked", "lines": 2, "long": "--unpacked" }, { "name": "--object-names", "lines": 3, "long": "--object-names" }, { "name": "--no-object-names", "lines": 45, "long": "--no-object-names" }, { "name": "--no-filter", "lines": 2, "long": "--no-filter" }, { "name": "--filter-provided-objects", "lines": 3, "long": "--filter-provided-objects" }, { "name": "--filter-print-omitted", "lines": 20, "long": "--filter-print-omitted" }, { "name": "--exclude-promisor-objects", "lines": 4, "long": "--exclude-promisor-objects" }, { "name": "--no-walk[=(sorted|unsorted)]", "lines": 6 }, { "name": "--do-walk", "lines": 2, "long": "--do-walk" }, { "name": "Commit Formatting", "lines": 15 }, { "name": "--abbrev-commit", "lines": 7, "long": "--abbrev-commit" }, { "name": "--no-abbrev-commit", "lines": 4, "long": "--no-abbrev-commit" }, { "name": "--oneline", "lines": 20, "long": "--oneline" }, { "name": "--show-signature", "lines": 3, "long": "--show-signature" }, { "name": "--relative-date", "lines": 57, "long": "--relative-date" }, { "name": "--header", "lines": 3, "long": "--header" }, { "name": "--no-commit-header", "lines": 4, "long": "--no-commit-header" }, { "name": "--commit-header", "lines": 2, "long": "--commit-header" }, { "name": "--parents", "lines": 3, "long": "--parents" }, { "name": "--children", "lines": 3, "long": "--children" }, { "name": "--timestamp", "lines": 2, "long": "--timestamp" }, { "name": "--left-right", "lines": 24, "long": "--left-right" }, { "name": "--graph", "lines": 15, "long": "--graph" }, { "name": "--count", "lines": 5, "long": "--count" } ] }, { "name": "PRETTY FORMATS", "lines": 441, "subsections": [] }, { "name": "EXAMPLES", "lines": 76, "subsections": [] }, { "name": "GIT", "lines": 5, "subsections": [] } ], "sections": { "NAME": { "content": "git-rev-list - Lists commit objects in reverse chronological order\n", "subsections": [] }, "SYNOPSIS": { "content": "git rev-list [] ... [[--] ...]\n\n", "subsections": [] }, "DESCRIPTION": { "content": "List commits that are reachable by following the parent links from the given commit(s), but\nexclude commits that are reachable from the one(s) given with a ^ in front of them. The\noutput is given in reverse chronological order by default.\n\nYou can think of this as a set operation. Commits reachable from any of the commits given on\nthe command line form a set, and then commits reachable from any of the ones given with ^ in\nfront are subtracted from that set. The remaining commits are what comes out in the command’s\noutput. Various other options and paths parameters can be used to further limit the result.\n\nThus, the following command:\n\n$ git rev-list foo bar ^baz\n\n\nmeans \"list all the commits which are reachable from foo or bar, but not from baz\".\n\nA special notation \"..\" can be used as a short-hand for \"^\n\". For example, either of the following may be used interchangeably:\n\n$ git rev-list origin..HEAD\n$ git rev-list HEAD ^origin\n\n\nAnother special notation is \"...\" which is useful for merges. The resulting\nset of commits is the symmetric difference between the two operands. The following two\ncommands are equivalent:\n\n$ git rev-list A B --not $(git merge-base --all A B)\n$ git rev-list A...B\n\n\nrev-list is a very essential Git command, since it provides the ability to build and traverse\ncommit ancestry graphs. For this reason, it has a lot of different options that enables it to\nbe used by commands as different as git bisect and git repack.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "Commit Limiting", "content": "Besides specifying a range of commits that should be listed using the special notations\nexplained in the description, additional commit limiting may be applied.\n\nUsing more options generally further limits the output (e.g. --since= limits to\ncommits newer than , and using it with --grep= further limits to commits\nwhose log message has a line that matches ), unless otherwise noted.\n\nNote that these are applied before commit ordering and formatting options, such as --reverse.\n\n-, -n , --max-count=\nLimit the number of commits to output.\n\n--skip=\nSkip number commits before starting to show the commit output.\n\n--since=, --after=\nShow commits more recent than a specific date.\n\n--until=, --before=\nShow commits older than a specific date.\n\n--max-age=, --min-age=\nLimit the commits output to specified time range.\n\n--author=, --committer=\nLimit the commits output to ones with author/committer header lines that match the\nspecified pattern (regular expression). With more than one --author=, commits\nwhose author matches any of the given patterns are chosen (similarly for multiple\n--committer=).\n\n--grep-reflog=\nLimit the commits output to ones with reflog entries that match the specified pattern\n(regular expression). With more than one --grep-reflog, commits whose reflog message\nmatches any of the given patterns are chosen. It is an error to use this option unless\n--walk-reflogs is in use.\n\n--grep=\nLimit the commits output to ones with log message that matches the specified pattern\n(regular expression). With more than one --grep=, commits whose message matches\nany of the given patterns are chosen (but see --all-match).\n" }, { "name": "--all-match", "content": "Limit the commits output to ones that match all given --grep, instead of ones that match\nat least one.\n", "long": "--all-match" }, { "name": "--invert-grep", "content": "Limit the commits output to ones with log message that do not match the pattern specified\nwith --grep=.\n", "long": "--invert-grep" }, { "name": "-i, --regexp-ignore-case", "content": "Match the regular expression limiting patterns without regard to letter case.\n", "flag": "-i", "long": "--regexp-ignore-case" }, { "name": "--basic-regexp", "content": "Consider the limiting patterns to be basic regular expressions; this is the default.\n", "long": "--basic-regexp" }, { "name": "-E, --extended-regexp", "content": "Consider the limiting patterns to be extended regular expressions instead of the default\nbasic regular expressions.\n", "flag": "-E", "long": "--extended-regexp" }, { "name": "-F, --fixed-strings", "content": "Consider the limiting patterns to be fixed strings (don’t interpret pattern as a regular\nexpression).\n", "flag": "-F", "long": "--fixed-strings" }, { "name": "-P, --perl-regexp", "content": "Consider the limiting patterns to be Perl-compatible regular expressions.\n\nSupport for these types of regular expressions is an optional compile-time dependency. If\nGit wasn’t compiled with support for them providing this option will cause it to die.\n", "flag": "-P", "long": "--perl-regexp" }, { "name": "--remove-empty", "content": "Stop when a given path disappears from the tree.\n", "long": "--remove-empty" }, { "name": "--merges", "content": "Print only merge commits. This is exactly the same as --min-parents=2.\n", "long": "--merges" }, { "name": "--no-merges", "content": "Do not print commits with more than one parent. This is exactly the same as\n--max-parents=1.\n\n--min-parents=, --max-parents=, --no-min-parents, --no-max-parents\nShow only commits which have at least (or at most) that many parent commits. In\nparticular, --max-parents=1 is the same as --no-merges, --min-parents=2 is the same as\n--merges. --max-parents=0 gives all root commits and --min-parents=3 all octopus merges.\n\n--no-min-parents and --no-max-parents reset these limits (to no limit) again. Equivalent\nforms are --min-parents=0 (any commit has 0 or more parents) and --max-parents=-1\n(negative numbers denote no upper limit).\n", "long": "--no-merges" }, { "name": "--first-parent", "content": "Follow only the first parent commit upon seeing a merge commit. This option can give a\nbetter overview when viewing the evolution of a particular topic branch, because merges\ninto a topic branch tend to be only about adjusting to updated upstream from time to\ntime, and this option allows you to ignore the individual commits brought in to your\nhistory by such a merge.\n", "long": "--first-parent" }, { "name": "--not", "content": "Reverses the meaning of the ^ prefix (or lack thereof) for all following revision\nspecifiers, up to the next --not.\n", "long": "--not" }, { "name": "--all", "content": "Pretend as if all the refs in refs/, along with HEAD, are listed on the command line as\n.\n\n--branches[=]\nPretend as if all the refs in refs/heads are listed on the command line as . If\n is given, limit branches to ones matching given shell glob. If pattern lacks ?,\n*, or [, /* at the end is implied.\n\n--tags[=]\nPretend as if all the refs in refs/tags are listed on the command line as . If\n is given, limit tags to ones matching given shell glob. If pattern lacks ?, *,\nor [, /* at the end is implied.\n\n--remotes[=]\nPretend as if all the refs in refs/remotes are listed on the command line as . If\n is given, limit remote-tracking branches to ones matching given shell glob. If\npattern lacks ?, *, or [, /* at the end is implied.\n\n--glob=\nPretend as if all the refs matching shell glob are listed on the command\nline as . Leading refs/, is automatically prepended if missing. If pattern lacks\n?, *, or [, /* at the end is implied.\n\n--exclude=\nDo not include refs matching that the next --all, --branches, --tags,\n--remotes, or --glob would otherwise consider. Repetitions of this option accumulate\nexclusion patterns up to the next --all, --branches, --tags, --remotes, or --glob option\n(other options or arguments do not clear accumulated patterns).\n\nThe patterns given should not begin with refs/heads, refs/tags, or refs/remotes when\napplied to --branches, --tags, or --remotes, respectively, and they must begin with refs/\nwhen applied to --glob or --all. If a trailing /* is intended, it must be given\nexplicitly.\n", "long": "--all" }, { "name": "--reflog", "content": "Pretend as if all objects mentioned by reflogs are listed on the command line as\n.\n", "long": "--reflog" }, { "name": "--alternate-refs", "content": "Pretend as if all objects mentioned as ref tips of alternate repositories were listed on\nthe command line. An alternate repository is any repository whose object directory is\nspecified in objects/info/alternates. The set of included objects may be modified by\ncore.alternateRefsCommand, etc. See git-config(1).\n", "long": "--alternate-refs" }, { "name": "--single-worktree", "content": "By default, all working trees will be examined by the following options when there are\nmore than one (see git-worktree(1)): --all, --reflog and --indexed-objects. This option\nforces them to examine the current working tree only.\n", "long": "--single-worktree" }, { "name": "--ignore-missing", "content": "Upon seeing an invalid object name in the input, pretend as if the bad input was not\ngiven.\n", "long": "--ignore-missing" }, { "name": "--stdin", "content": "In addition to the listed on the command line, read them from the standard\ninput. If a -- separator is seen, stop reading commits and start reading paths to limit\nthe result.\n", "long": "--stdin" }, { "name": "--quiet", "content": "Don’t print anything to standard output. This form is primarily meant to allow the caller\nto test the exit status to see if a range of objects is fully connected (or not). It is\nfaster than redirecting stdout to /dev/null as the output does not have to be formatted.\n", "long": "--quiet" }, { "name": "--disk-usage", "content": "Suppress normal output; instead, print the sum of the bytes used for on-disk storage by\nthe selected commits or objects. This is equivalent to piping the output into git\ncat-file --batch-check='%(objectsize:disk)', except that it runs much faster (especially\nwith --use-bitmap-index). See the CAVEATS section in git-cat-file(1) for the limitations\nof what \"on-disk storage\" means.\n", "long": "--disk-usage" }, { "name": "--cherry-mark", "content": "Like --cherry-pick (see below) but mark equivalent commits with = rather than omitting\nthem, and inequivalent ones with +.\n", "long": "--cherry-mark" }, { "name": "--cherry-pick", "content": "Omit any commit that introduces the same change as another commit on the “other side”\nwhen the set of commits are limited with symmetric difference.\n\nFor example, if you have two branches, A and B, a usual way to list all commits on only\none side of them is with --left-right (see the example below in the description of the\n--left-right option). However, it shows the commits that were cherry-picked from the\nother branch (for example, “3rd on b” may be cherry-picked from branch A). With this\noption, such pairs of commits are excluded from the output.\n", "long": "--cherry-pick" }, { "name": "--left-only, --right-only", "content": "List only commits on the respective side of a symmetric difference, i.e. only those which\nwould be marked < resp. > by --left-right.\n\nFor example, --cherry-pick --right-only A...B omits those commits from B which are in A\nor are patch-equivalent to a commit in A. In other words, this lists the + commits from\ngit cherry A B. More precisely, --cherry-pick --right-only --no-merges gives the exact\nlist.\n", "long": "--right-only" }, { "name": "--cherry", "content": "A synonym for --right-only --cherry-mark --no-merges; useful to limit the output to the\ncommits on our side and mark those that have been applied to the other side of a forked\nhistory with git log --cherry upstream...mybranch, similar to git cherry upstream\nmybranch.\n", "long": "--cherry" }, { "name": "-g, --walk-reflogs", "content": "Instead of walking the commit ancestry chain, walk reflog entries from the most recent\none to older ones. When this option is used you cannot specify commits to exclude (that\nis, ^commit, commit1..commit2, and commit1...commit2 notations cannot be used).\n\nWith --pretty format other than oneline and reference (for obvious reasons), this causes\nthe output to have two extra lines of information taken from the reflog. The reflog\ndesignator in the output may be shown as ref@{Nth} (where Nth is the\nreverse-chronological index in the reflog) or as ref@{timestamp} (with the timestamp for\nthat entry), depending on a few rules:\n\n1. If the starting point is specified as ref@{Nth}, show the index format.\n\n2. If the starting point was specified as ref@{now}, show the timestamp format.\n\n3. If neither was used, but --date was given on the command line, show the timestamp in\nthe format requested by --date.\n\n4. Otherwise, show the index format.\n\nUnder --pretty=oneline, the commit message is prefixed with this information on the same\nline. This option cannot be combined with --reverse. See also git-reflog(1).\n\nUnder --pretty=reference, this information will not be shown at all.\n", "flag": "-g", "long": "--walk-reflogs" }, { "name": "--merge", "content": "After a failed merge, show refs that touch files having a conflict and don’t exist on all\nheads to merge.\n", "long": "--merge" }, { "name": "--boundary", "content": "Output excluded boundary commits. Boundary commits are prefixed with -.\n", "long": "--boundary" }, { "name": "--use-bitmap-index", "content": "Try to speed up the traversal using the pack bitmap index (if one is available). Note\nthat when traversing with --objects, trees and blobs will not have their associated path\nprinted.\n\n--progress=
\nShow progress reports on stderr as objects are considered. The
text will be\nprinted with each progress update.\n", "long": "--use-bitmap-index" }, { "name": "History Simplification", "content": "Sometimes you are only interested in parts of the history, for example the commits modifying\na particular . But there are two parts of History Simplification, one part is selecting\nthe commits and the other is how to do it, as there are various strategies to simplify the\nhistory.\n\nThe following options select the commits to be shown:\n\n\nCommits modifying the given are selected.\n" }, { "name": "--simplify-by-decoration", "content": "Commits that are referred by some branch or tag are selected.\n\nNote that extra commits can be shown to give a meaningful history.\n\nThe following options affect the way the simplification is performed:\n\nDefault mode\nSimplifies the history to the simplest history explaining the final state of the tree.\nSimplest because it prunes some side branches if the end result is the same (i.e. merging\nbranches with the same content)\n", "long": "--simplify-by-decoration" }, { "name": "--show-pulls", "content": "Include all commits from the default mode, but also any merge commits that are not\nTREESAME to the first parent but are TREESAME to a later parent. This mode is helpful for\nshowing the merge commits that \"first introduced\" a change to a branch.\n", "long": "--show-pulls" }, { "name": "--full-history", "content": "Same as the default mode, but does not prune some history.\n", "long": "--full-history" }, { "name": "--dense", "content": "Only the selected commits are shown, plus some to have a meaningful history.\n", "long": "--dense" }, { "name": "--sparse", "content": "All commits in the simplified history are shown.\n", "long": "--sparse" }, { "name": "--simplify-merges", "content": "Additional option to --full-history to remove some needless merges from the resulting\nhistory, as there are no selected commits contributing to this merge.\n", "long": "--simplify-merges" }, { "name": "--ancestry-path", "content": "When given a range of commits to display (e.g. commit1..commit2 or commit2 ^commit1),\nonly display commits that exist directly on the ancestry chain between the commit1 and\ncommit2, i.e. commits that are both descendants of commit1, and ancestors of commit2.\n\nA more detailed explanation follows.\n\nSuppose you specified foo as the . We shall call commits that modify foo !TREESAME,\nand the rest TREESAME. (In a diff filtered for foo, they look different and equal,\nrespectively.)\n\nIn the following, we will always refer to the same example history to illustrate the\ndifferences between simplification settings. We assume that you are filtering for a file foo\nin this commit graph:\n\n.-A---M---N---O---P---Q\n/ / / / / /\nI B C D E Y\n\\ / / / / /\n`-------------' X\n\n\nThe horizontal line of history A---Q is taken to be the first parent of each merge. The\ncommits are:\n\n• I is the initial commit, in which foo exists with contents “asdf”, and a file quux exists\nwith contents “quux”. Initial commits are compared to an empty tree, so I is !TREESAME.\n\n• In A, foo contains just “foo”.\n\n• B contains the same change as A. Its merge M is trivial and hence TREESAME to all\nparents.\n\n• C does not change foo, but its merge N changes it to “foobar”, so it is not TREESAME to\nany parent.\n\n• D sets foo to “baz”. Its merge O combines the strings from N and D to “foobarbaz”; i.e.,\nit is not TREESAME to any parent.\n\n• E changes quux to “xyzzy”, and its merge P combines the strings to “quux xyzzy”. P is\nTREESAME to O, but not to E.\n\n• X is an independent root commit that added a new file side, and Y modified it. Y is\nTREESAME to X. Its merge Q added side to P, and Q is TREESAME to P, but not to Y.\n\nrev-list walks backwards through history, including or excluding commits based on whether\n--full-history and/or parent rewriting (via --parents or --children) are used. The following\nsettings are available.\n\nDefault mode\nCommits are included if they are not TREESAME to any parent (though this can be changed,\nsee --sparse below). If the commit was a merge, and it was TREESAME to one parent, follow\nonly that parent. (Even if there are several TREESAME parents, follow only one of them.)\nOtherwise, follow all parents.\n\nThis results in:\n\n.-A---N---O\n/ / /\nI---------D\n\nNote how the rule to only follow the TREESAME parent, if one is available, removed B from\nconsideration entirely. C was considered via N, but is TREESAME. Root commits are\ncompared to an empty tree, so I is !TREESAME.\n\nParent/child relations are only visible with --parents, but that does not affect the\ncommits selected in default mode, so we have shown the parent lines.\n\n--full-history without parent rewriting\nThis mode differs from the default in one point: always follow all parents of a merge,\neven if it is TREESAME to one of them. Even if more than one side of the merge has\ncommits that are included, this does not imply that the merge itself is! In the example,\nwe get\n\nI A B N D O P Q\n\nM was excluded because it is TREESAME to both parents. E, C and B were all walked, but\nonly B was !TREESAME, so the others do not appear.\n\nNote that without parent rewriting, it is not really possible to talk about the\nparent/child relationships between the commits, so we show them disconnected.\n\n--full-history with parent rewriting\nOrdinary commits are only included if they are !TREESAME (though this can be changed, see\n--sparse below).\n\nMerges are always included. However, their parent list is rewritten: Along each parent,\nprune away commits that are not included themselves. This results in\n\n.-A---M---N---O---P---Q\n/ / / / /\nI B / D /\n\\ / / / /\n`-------------'\n\nCompare to --full-history without rewriting above. Note that E was pruned away because it\nis TREESAME, but the parent list of P was rewritten to contain E's parent I. The same\nhappened for C and N, and X, Y and Q.\n\nIn addition to the above settings, you can change whether TREESAME affects inclusion:\n", "long": "--ancestry-path" }, { "name": "--dense", "content": "Commits that are walked are included if they are not TREESAME to any parent.\n", "long": "--dense" }, { "name": "--sparse", "content": "All commits that are walked are included.\n\nNote that without --full-history, this still simplifies merges: if one of the parents is\nTREESAME, we follow only that one, so the other sides of the merge are never walked.\n", "long": "--sparse" }, { "name": "--simplify-merges", "content": "First, build a history graph in the same way that --full-history with parent rewriting\ndoes (see above).\n\nThen simplify each commit C to its replacement C' in the final history according to the\nfollowing rules:\n\n• Set C' to C.\n\n• Replace each parent P of C' with its simplification P'. In the process, drop parents\nthat are ancestors of other parents or that are root commits TREESAME to an empty\ntree, and remove duplicates, but take care to never drop all parents that we are\nTREESAME to.\n\n• If after this parent rewriting, C' is a root or merge commit (has zero or >1\nparents), a boundary commit, or !TREESAME, it remains. Otherwise, it is replaced with\nits only parent.\n\nThe effect of this is best shown by way of comparing to --full-history with parent\nrewriting. The example turns into:\n\n.-A---M---N---O\n/ / /\nI B D\n\\ / /\n`---------'\n\nNote the major differences in N, P, and Q over --full-history:\n\n• N's parent list had I removed, because it is an ancestor of the other parent M.\nStill, N remained because it is !TREESAME.\n\n• P's parent list similarly had I removed. P was then removed completely, because it\nhad one parent and is TREESAME.\n\n• Q's parent list had Y simplified to X. X was then removed, because it was a TREESAME\nroot. Q was then removed completely, because it had one parent and is TREESAME.\n\nThere is another simplification mode available:\n", "long": "--simplify-merges" }, { "name": "--ancestry-path", "content": "Limit the displayed commits to those directly on the ancestry chain between the “from”\nand “to” commits in the given commit range. I.e. only display commits that are ancestor\nof the “to” commit and descendants of the “from” commit.\n\nAs an example use case, consider the following commit history:\n\nD---E-------F\n/ \\ \\\nB---C---G---H---I---J\n/ \\\nA-------K---------------L--M\n\nA regular D..M computes the set of commits that are ancestors of M, but excludes the ones\nthat are ancestors of D. This is useful to see what happened to the history leading to M\nsince D, in the sense that “what does M have that did not exist in D”. The result in this\nexample would be all the commits, except A and B (and D itself, of course).\n\nWhen we want to find out what commits in M are contaminated with the bug introduced by D\nand need fixing, however, we might want to view only the subset of D..M that are actually\ndescendants of D, i.e. excluding C and K. This is exactly what the --ancestry-path option\ndoes. Applied to the D..M range, it results in:\n\nE-------F\n\\ \\\nG---H---I---J\n\\\nL--M\n\n\nBefore discussing another option, --show-pulls, we need to create a new example history.\n\nA common problem users face when looking at simplified history is that a commit they know\nchanged a file somehow does not appear in the file’s simplified history. Let’s demonstrate a\nnew example and show how options such as --full-history and --simplify-merges works in that\ncase:\n\n.-A---M-----C--N---O---P\n/ / \\ \\ \\/ / /\nI B \\ R-'`-Z' /\n\\ / \\/ /\n\\ / /\\ /\n`---X--' `---Y--'\n\n\nFor this example, suppose I created file.txt which was modified by A, B, and X in different\nways. The single-parent commits C, Z, and Y do not change file.txt. The merge commit M was\ncreated by resolving the merge conflict to include both changes from A and B and hence is not\nTREESAME to either. The merge commit R, however, was created by ignoring the contents of\nfile.txt at M and taking only the contents of file.txt at X. Hence, R is TREESAME to X but\nnot M. Finally, the natural merge resolution to create N is to take the contents of file.txt\nat R, so N is TREESAME to R but not C. The merge commits O and P are TREESAME to their first\nparents, but not to their second parents, Z and Y respectively.\n\nWhen using the default mode, N and R both have a TREESAME parent, so those edges are walked\nand the others are ignored. The resulting history graph is:\n\nI---X\n\n\nWhen using --full-history, Git walks every edge. This will discover the commits A and B and\nthe merge M, but also will reveal the merge commits O and P. With parent rewriting, the\nresulting graph is:\n\n.-A---M--------N---O---P\n/ / \\ \\ \\/ / /\nI B \\ R-'`--' /\n\\ / \\/ /\n\\ / /\\ /\n`---X--' `------'\n\n\nHere, the merge commits O and P contribute extra noise, as they did not actually contribute a\nchange to file.txt. They only merged a topic that was based on an older version of file.txt.\nThis is a common issue in repositories using a workflow where many contributors work in\nparallel and merge their topic branches along a single trunk: manu unrelated merges appear in\nthe --full-history results.\n\nWhen using the --simplify-merges option, the commits O and P disappear from the results. This\nis because the rewritten second parents of O and P are reachable from their first parents.\nThose edges are removed and then the commits look like single-parent commits that are\nTREESAME to their parent. This also happens to the commit N, resulting in a history view as\nfollows:\n\n.-A---M--.\n/ / \\\nI B R\n\\ / /\n\\ / /\n`---X--'\n\n\nIn this view, we see all of the important single-parent changes from A, B, and X. We also see\nthe carefully-resolved merge M and the not-so-carefully-resolved merge R. This is usually\nenough information to determine why the commits A and B \"disappeared\" from history in the\ndefault view. However, there are a few issues with this approach.\n\nThe first issue is performance. Unlike any previous option, the --simplify-merges option\nrequires walking the entire commit history before returning a single result. This can make\nthe option difficult to use for very large repositories.\n\nThe second issue is one of auditing. When many contributors are working on the same\nrepository, it is important which merge commits introduced a change into an important branch.\nThe problematic merge R above is not likely to be the merge commit that was used to merge\ninto an important branch. Instead, the merge N was used to merge R and X into the important\nbranch. This commit may have information about why the change X came to override the changes\nfrom A and B in its commit message.\n", "long": "--ancestry-path" }, { "name": "--show-pulls", "content": "In addition to the commits shown in the default history, show each merge commit that is\nnot TREESAME to its first parent but is TREESAME to a later parent.\n\nWhen a merge commit is included by --show-pulls, the merge is treated as if it \"pulled\"\nthe change from another branch. When using --show-pulls on this example (and no other\noptions) the resulting graph is:\n\nI---X---R---N\n\nHere, the merge commits R and N are included because they pulled the commits X and R into\nthe base branch, respectively. These merges are the reason the commits A and B do not\nappear in the default history.\n\nWhen --show-pulls is paired with --simplify-merges, the graph includes all of the\nnecessary information:\n\n.-A---M--. N\n/ / \\ /\nI B R\n\\ / /\n\\ / /\n`---X--'\n\nNotice that since M is reachable from R, the edge from N to M was simplified away.\nHowever, N still appears in the history as an important commit because it \"pulled\" the\nchange R into the main branch.\n\nThe --simplify-by-decoration option allows you to view only the big picture of the topology\nof the history, by omitting commits that are not referenced by tags. Commits are marked as\n!TREESAME (in other words, kept after history simplification rules described above) if (1)\nthey are referenced by tags, or (2) they change the contents of the paths given on the\ncommand line. All other commits are marked as TREESAME (subject to be simplified away).\n", "long": "--show-pulls" }, { "name": "Bisection Helpers", "content": "" }, { "name": "--bisect", "content": "Limit output to the one commit object which is roughly halfway between included and\nexcluded commits. Note that the bad bisection ref refs/bisect/bad is added to the\nincluded commits (if it exists) and the good bisection refs refs/bisect/good-* are added\nto the excluded commits (if they exist). Thus, supposing there are no refs in\nrefs/bisect/, if\n\n$ git rev-list --bisect foo ^bar ^baz\n\noutputs midpoint, the output of the two commands\n\n$ git rev-list foo ^midpoint\n$ git rev-list midpoint ^bar ^baz\n\nwould be of roughly the same length. Finding the change which introduces a regression is\nthus reduced to a binary search: repeatedly generate and test new 'midpoint’s until the\ncommit chain is of length one.\n", "long": "--bisect" }, { "name": "--bisect-vars", "content": "This calculates the same as --bisect, except that refs in refs/bisect/ are not used, and\nexcept that this outputs text ready to be eval’ed by the shell. These lines will assign\nthe name of the midpoint revision to the variable bisectrev, and the expected number of\ncommits to be tested after bisectrev is tested to bisectnr, the expected number of\ncommits to be tested if bisectrev turns out to be good to bisectgood, the expected\nnumber of commits to be tested if bisectrev turns out to be bad to bisectbad, and the\nnumber of commits we are bisecting right now to bisectall.\n", "long": "--bisect-vars" }, { "name": "--bisect-all", "content": "This outputs all the commit objects between the included and excluded commits, ordered by\ntheir distance to the included and excluded commits. Refs in refs/bisect/ are not used.\nThe farthest from them is displayed first. (This is the only one displayed by --bisect.)\n\nThis is useful because it makes it easy to choose a good commit to test when you want to\navoid to test some of them for some reason (they may not compile for example).\n\nThis option can be used along with --bisect-vars, in this case, after all the sorted\ncommit objects, there will be the same text as if --bisect-vars had been used alone.\n", "long": "--bisect-all" }, { "name": "Commit Ordering", "content": "By default, the commits are shown in reverse chronological order.\n" }, { "name": "--date-order", "content": "Show no parents before all of its children are shown, but otherwise show commits in the\ncommit timestamp order.\n", "long": "--date-order" }, { "name": "--author-date-order", "content": "Show no parents before all of its children are shown, but otherwise show commits in the\nauthor timestamp order.\n", "long": "--author-date-order" }, { "name": "--topo-order", "content": "Show no parents before all of its children are shown, and avoid showing commits on\nmultiple lines of history intermixed.\n\nFor example, in a commit history like this:\n\n---1----2----4----7\n\\ \\\n3----5----6----8---\n\nwhere the numbers denote the order of commit timestamps, git rev-list and friends with\n--date-order show the commits in the timestamp order: 8 7 6 5 4 3 2 1.\n\nWith --topo-order, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5 3 1); some older\ncommits are shown before newer ones in order to avoid showing the commits from two\nparallel development track mixed together.\n", "long": "--topo-order" }, { "name": "--reverse", "content": "Output the commits chosen to be shown (see Commit Limiting section above) in reverse\norder. Cannot be combined with --walk-reflogs.\n", "long": "--reverse" }, { "name": "Object Traversal", "content": "These options are mostly targeted for packing of Git repositories.\n" }, { "name": "--objects", "content": "Print the object IDs of any object referenced by the listed commits. --objects foo ^bar\nthus means “send me all object IDs which I need to download if I have the commit object\nbar but not foo”.\n", "long": "--objects" }, { "name": "--in-commit-order", "content": "Print tree and blob ids in order of the commits. The tree and blob ids are printed after\nthey are first referenced by a commit.\n", "long": "--in-commit-order" }, { "name": "--objects-edge", "content": "Similar to --objects, but also print the IDs of excluded commits prefixed with a “-”\ncharacter. This is used by git-pack-objects(1) to build a “thin” pack, which records\nobjects in deltified form based on objects contained in these excluded commits to reduce\nnetwork traffic.\n", "long": "--objects-edge" }, { "name": "--objects-edge-aggressive", "content": "Similar to --objects-edge, but it tries harder to find excluded commits at the cost of\nincreased time. This is used instead of --objects-edge to build “thin” packs for shallow\nrepositories.\n", "long": "--objects-edge-aggressive" }, { "name": "--indexed-objects", "content": "Pretend as if all trees and blobs used by the index are listed on the command line. Note\nthat you probably want to use --objects, too.\n", "long": "--indexed-objects" }, { "name": "--unpacked", "content": "Only useful with --objects; print the object IDs that are not in packs.\n", "long": "--unpacked" }, { "name": "--object-names", "content": "Only useful with --objects; print the names of the object IDs that are found. This is the\ndefault behavior.\n", "long": "--object-names" }, { "name": "--no-object-names", "content": "Only useful with --objects; does not print the names of the object IDs that are found.\nThis inverts --object-names. This flag allows the output to be more easily parsed by\ncommands such as git-cat-file(1).\n\n--filter=\nOnly useful with one of the --objects*; omits objects (usually blobs) from the list of\nprinted objects. The may be one of the following:\n\nThe form --filter=blob:none omits all blobs.\n\nThe form --filter=blob:limit=[kmg] omits blobs larger than n bytes or units. n may be\nzero. The suffixes k, m, and g can be used to name units in KiB, MiB, or GiB. For\nexample, blob:limit=1k is the same as blob:limit=1024.\n\nThe form --filter=object:type=(tag|commit|tree|blob) omits all objects which are not of\nthe requested type.\n\nThe form --filter=sparse:oid= uses a sparse-checkout specification contained in\nthe blob (or blob-expression) to omit blobs that would not be required for a\nsparse checkout on the requested refs.\n\nThe form --filter=tree: omits all blobs and trees whose depth from the root tree\nis >= (minimum depth if an object is located at multiple depths in the commits\ntraversed). =0 will not include any trees or blobs unless included explicitly in\nthe command-line (or standard input when --stdin is used). =1 will include only\nthe tree and blobs which are referenced directly by a commit reachable from or\nan explicitly-given object. =2 is like =1 while also including trees and\nblobs one more level removed from an explicitly-given commit or tree.\n\nNote that the form --filter=sparse:path= that wants to read from an arbitrary path\non the filesystem has been dropped for security reasons.\n\nMultiple --filter= flags can be specified to combine filters. Only objects which are\naccepted by every filter are included.\n\nThe form --filter=combine:++... can also be used to combined\nseveral filters, but this is harder than just repeating the --filter flag and is usually\nnot necessary. Filters are joined by + and individual filters are %-encoded (i.e.\nURL-encoded). Besides the + and % characters, the following characters are reserved and\nalso must be encoded: ~!@#$^&*()[]{}\\;\",<>?'` as well as all characters with ASCII code\n<= 0x20, which includes space and newline.\n\nOther arbitrary characters can also be encoded. For instance, combine:tree:3+blob:none\nand combine:tree%3A3+blob%3Anone are equivalent.\n", "long": "--no-object-names" }, { "name": "--no-filter", "content": "Turn off any previous --filter= argument.\n", "long": "--no-filter" }, { "name": "--filter-provided-objects", "content": "Filter the list of explicitly provided objects, which would otherwise always be printed\neven if they did not match any of the filters. Only useful with --filter=.\n", "long": "--filter-provided-objects" }, { "name": "--filter-print-omitted", "content": "Only useful with --filter=; prints a list of the objects omitted by the filter. Object\nIDs are prefixed with a “~” character.\n\n--missing=\nA debug option to help with future \"partial clone\" development. This option specifies how\nmissing objects are handled.\n\nThe form --missing=error requests that rev-list stop with an error if a missing object is\nencountered. This is the default action.\n\nThe form --missing=allow-any will allow object traversal to continue if a missing object\nis encountered. Missing objects will silently be omitted from the results.\n\nThe form --missing=allow-promisor is like allow-any, but will only allow object traversal\nto continue for EXPECTED promisor missing objects. Unexpected missing objects will raise\nan error.\n\nThe form --missing=print is like allow-any, but will also print a list of the missing\nobjects. Object IDs are prefixed with a “?” character.\n", "long": "--filter-print-omitted" }, { "name": "--exclude-promisor-objects", "content": "(For internal use only.) Prefilter object traversal at promisor boundary. This is used\nwith partial clone. This is stronger than --missing=allow-promisor because it limits the\ntraversal, rather than just silencing errors about missing objects.\n", "long": "--exclude-promisor-objects" }, { "name": "--no-walk[=(sorted|unsorted)]", "content": "Only show the given commits, but do not traverse their ancestors. This has no effect if a\nrange is specified. If the argument unsorted is given, the commits are shown in the order\nthey were given on the command line. Otherwise (if sorted or no argument was given), the\ncommits are shown in reverse chronological order by commit time. Cannot be combined with\n--graph.\n" }, { "name": "--do-walk", "content": "Overrides a previous --no-walk.\n", "long": "--do-walk" }, { "name": "Commit Formatting", "content": "Using these options, git-rev-list(1) will act similar to the more specialized family of\ncommit log tools: git-log(1), git-show(1), and git-whatchanged(1)\n\n--pretty[=], --format=\nPretty-print the contents of the commit logs in a given format, where can be one\nof oneline, short, medium, full, fuller, reference, email, raw, format: and\ntformat:. When is none of the above, and has %placeholder in it, it acts\nas if --pretty=tformat: were given.\n\nSee the \"PRETTY FORMATS\" section for some additional details for each format. When\n= part is omitted, it defaults to medium.\n\nNote: you can specify the default pretty format in the repository configuration (see git-\nconfig(1)).\n" }, { "name": "--abbrev-commit", "content": "Instead of showing the full 40-byte hexadecimal commit object name, show a prefix that\nnames the object uniquely. \"--abbrev=\" (which also modifies diff output, if it is\ndisplayed) option can be used to specify the minimum length of the prefix.\n\nThis should make \"--pretty=oneline\" a whole lot more readable for people using 80-column\nterminals.\n", "long": "--abbrev-commit" }, { "name": "--no-abbrev-commit", "content": "Show the full 40-byte hexadecimal commit object name. This negates --abbrev-commit,\neither explicit or implied by other options such as \"--oneline\". It also overrides the\nlog.abbrevCommit variable.\n", "long": "--no-abbrev-commit" }, { "name": "--oneline", "content": "This is a shorthand for \"--pretty=oneline --abbrev-commit\" used together.\n\n--encoding=\nCommit objects record the character encoding used for the log message in their encoding\nheader; this option can be used to tell the command to re-code the commit log message in\nthe encoding preferred by the user. For non plumbing commands this defaults to UTF-8.\nNote that if an object claims to be encoded in X and we are outputting in X, we will\noutput the object verbatim; this means that invalid sequences in the original commit may\nbe copied to the output. Likewise, if iconv(3) fails to convert the commit, we will\nquietly output the original object verbatim.\n\n--expand-tabs=, --expand-tabs, --no-expand-tabs\nPerform a tab expansion (replace each tab with enough spaces to fill to the next display\ncolumn that is multiple of ) in the log message before showing it in the output.\n--expand-tabs is a short-hand for --expand-tabs=8, and --no-expand-tabs is a short-hand\nfor --expand-tabs=0, which disables tab expansion.\n\nBy default, tabs are expanded in pretty formats that indent the log message by 4 spaces\n(i.e. medium, which is the default, full, and fuller).\n", "long": "--oneline" }, { "name": "--show-signature", "content": "Check the validity of a signed commit object by passing the signature to gpg --verify and\nshow the output.\n", "long": "--show-signature" }, { "name": "--relative-date", "content": "Synonym for --date=relative.\n\n--date=\nOnly takes effect for dates shown in human-readable format, such as when using --pretty.\nlog.date config variable sets a default value for the log command’s --date option. By\ndefault, dates are shown in the original time zone (either committer’s or author’s). If\n-local is appended to the format (e.g., iso-local), the user’s local time zone is used\ninstead.\n\n--date=relative shows dates relative to the current time, e.g. “2 hours ago”. The -local\noption has no effect for --date=relative.\n\n--date=local is an alias for --date=default-local.\n\n--date=iso (or --date=iso8601) shows timestamps in a ISO 8601-like format. The\ndifferences to the strict ISO 8601 format are:\n\n• a space instead of the T date/time delimiter\n\n• a space between time and time zone\n\n• no colon between hours and minutes of the time zone\n\n--date=iso-strict (or --date=iso8601-strict) shows timestamps in strict ISO 8601 format.\n\n--date=rfc (or --date=rfc2822) shows timestamps in RFC 2822 format, often found in email\nmessages.\n\n--date=short shows only the date, but not the time, in YYYY-MM-DD format.\n\n--date=raw shows the date as seconds since the epoch (1970-01-01 00:00:00 UTC), followed\nby a space, and then the timezone as an offset from UTC (a + or - with four digits; the\nfirst two are hours, and the second two are minutes). I.e., as if the timestamp were\nformatted with strftime(\"%s %z\")). Note that the -local option does not affect the\nseconds-since-epoch value (which is always measured in UTC), but does switch the\naccompanying timezone value.\n\n--date=human shows the timezone if the timezone does not match the current time-zone, and\ndoesn’t print the whole date if that matches (ie skip printing year for dates that are\n\"this year\", but also skip the whole date itself if it’s in the last few days and we can\njust say what weekday it was). For older dates the hour and minute is also omitted.\n\n--date=unix shows the date as a Unix epoch timestamp (seconds since 1970). As with --raw,\nthis is always in UTC and therefore -local has no effect.\n\n--date=format:... feeds the format ... to your system strftime, except for %z and %Z,\nwhich are handled internally. Use --date=format:%c to show the date in your system\nlocale’s preferred format. See the strftime manual for a complete list of format\nplaceholders. When using -local, the correct syntax is --date=format-local:....\n\n--date=default is the default format, and is similar to --date=rfc2822, with a few\nexceptions:\n\n• there is no comma after the day-of-week\n\n• the time zone is omitted when the local time zone is used\n", "long": "--relative-date" }, { "name": "--header", "content": "Print the contents of the commit in raw-format; each record is separated with a NUL\ncharacter.\n", "long": "--header" }, { "name": "--no-commit-header", "content": "Suppress the header line containing \"commit\" and the object ID printed before the\nspecified format. This has no effect on the built-in formats; only custom formats are\naffected.\n", "long": "--no-commit-header" }, { "name": "--commit-header", "content": "Overrides a previous --no-commit-header.\n", "long": "--commit-header" }, { "name": "--parents", "content": "Print also the parents of the commit (in the form \"commit parent...\"). Also enables\nparent rewriting, see History Simplification above.\n", "long": "--parents" }, { "name": "--children", "content": "Print also the children of the commit (in the form \"commit child...\"). Also enables\nparent rewriting, see History Simplification above.\n", "long": "--children" }, { "name": "--timestamp", "content": "Print the raw commit timestamp.\n", "long": "--timestamp" }, { "name": "--left-right", "content": "Mark which side of a symmetric difference a commit is reachable from. Commits from the\nleft side are prefixed with < and those from the right with >. If combined with\n--boundary, those commits are prefixed with -.\n\nFor example, if you have this topology:\n\ny---b---b branch B\n/ \\ /\n/ .\n/ / \\\no---x---a---a branch A\n\nyou would get an output like this:\n\n$ git rev-list --left-right --boundary --pretty=oneline A...B\n\n>bbbbbbb... 3rd on b\n>bbbbbbb... 2nd on b\n]\nWhen --graph is not used, all history branches are flattened which can make it hard to\nsee that the two consecutive commits do not belong to a linear branch. This option puts a\nbarrier in between them in that case. If is specified, it is the string that\nwill be shown instead of the default one.\n", "long": "--graph" }, { "name": "--count", "content": "Print a number stating how many commits would have been listed, and suppress all other\noutput. When used together with --left-right, instead print the counts for left and right\ncommits, separated by a tab. When used together with --cherry-mark, omit patch equivalent\ncommits from these counts and print the count for equivalent commits separated by a tab.\n", "long": "--count" } ] }, "PRETTY FORMATS": { "content": "If the commit is a merge, and if the pretty-format is not oneline, email or raw, an\nadditional line is inserted before the Author: line. This line begins with \"Merge: \" and the\nhashes of ancestral commits are printed, separated by spaces. Note that the listed commits\nmay not necessarily be the list of the direct parent commits if you have limited your view of\nhistory: for example, if you are only interested in changes related to a certain directory or\nfile.\n\nThere are several built-in formats, and you can define additional formats by setting a\npretty. config option to either another format name, or a format: string, as described\nbelow (see git-config(1)). Here are the details of the built-in formats:\n\n• oneline\n\n \n\nThis is designed to be as compact as possible.\n\n• short\n\ncommit <hash>\nAuthor: <author>\n\n<title line>\n\n• medium\n\ncommit <hash>\nAuthor: <author>\nDate: <author date>\n\n<title line>\n\n<full commit message>\n\n• full\n\ncommit <hash>\nAuthor: <author>\nCommit: <committer>\n\n<title line>\n\n<full commit message>\n\n• fuller\n\ncommit <hash>\nAuthor: <author>\nAuthorDate: <author date>\nCommit: <committer>\nCommitDate: <committer date>\n\n<title line>\n\n<full commit message>\n\n• reference\n\n<abbrev hash> (<title line>, <short author date>)\n\nThis format is used to refer to another commit in a commit message and is the same as\n--pretty='format:%C(auto)%h (%s, %ad)'. By default, the date is formatted with\n--date=short unless another --date option is explicitly specified. As with any format:\nwith format placeholders, its output is not affected by other options like --decorate and\n--walk-reflogs.\n\n• email\n\nFrom <hash> <date>\nFrom: <author>\nDate: <author date>\nSubject: [PATCH] <title line>\n\n<full commit message>\n\n• mboxrd\n\nLike email, but lines in the commit message starting with \"From \" (preceded by zero or\nmore \">\") are quoted with \">\" so they aren’t confused as starting a new commit.\n\n• raw\n\nThe raw format shows the entire commit exactly as stored in the commit object. Notably,\nthe hashes are displayed in full, regardless of whether --abbrev or --no-abbrev are used,\nand parents information show the true parent commits, without taking grafts or history\nsimplification into account. Note that this format affects the way commits are displayed,\nbut not the way the diff is shown e.g. with git log --raw. To get full object names in a\nraw diff format, use --no-abbrev.\n\n• format:<string>\n\nThe format:<string> format allows you to specify which information you want to show. It\nworks a little bit like printf format, with the notable exception that you get a newline\nwith %n instead of \\n.\n\nE.g, format:\"The author of %h was %an, %ar%nThe title was >>%s<<%n\" would show something\nlike this:\n\nThe author of fe6e0ee was Junio C Hamano, 23 hours ago\nThe title was >>t4119: test autocomputing -p<n> for traditional diff input.<<\n\nThe placeholders are:\n\n• Placeholders that expand to a single literal character:\n\n%n\nnewline\n\n%%\na raw %\n\n%x00\nprint a byte from a hex code\n\n• Placeholders that affect formatting of later placeholders:\n\n%Cred\nswitch color to red\n\n%Cgreen\nswitch color to green\n\n%Cblue\nswitch color to blue\n\n%Creset\nreset color\n\n%C(...)\ncolor specification, as described under Values in the \"CONFIGURATION FILE\"\nsection of git-config(1). By default, colors are shown only when enabled for log\noutput (by color.diff, color.ui, or --color, and respecting the auto settings of\nthe former if we are going to a terminal). %C(auto,...) is accepted as a\nhistorical synonym for the default (e.g., %C(auto,red)). Specifying\n%C(always,...) will show the colors even when color is not otherwise enabled\n(though consider just using --color=always to enable color for the whole output,\nincluding this format and anything else git might color). auto alone (i.e.\n%C(auto)) will turn on auto coloring on the next placeholders until the color is\nswitched again.\n\n%m\nleft (<), right (>) or boundary (-) mark\n\n%w([<w>[,<i1>[,<i2>]]])\nswitch line wrapping, like the -w option of git-shortlog(1).\n\n%<(<N>[,trunc|ltrunc|mtrunc])\nmake the next placeholder take at least N columns, padding spaces on the right if\nnecessary. Optionally truncate at the beginning (ltrunc), the middle (mtrunc) or\nthe end (trunc) if the output is longer than N columns. Note that truncating only\nworks correctly with N >= 2.\n\n%<|(<N>)\nmake the next placeholder take at least until Nth columns, padding spaces on the\nright if necessary\n\n%>(<N>), %>|(<N>)\nsimilar to %<(<N>), %<|(<N>) respectively, but padding spaces on the left\n\n%>>(<N>), %>>|(<N>)\nsimilar to %>(<N>), %>|(<N>) respectively, except that if the next placeholder\ntakes more spaces than given and there are spaces on its left, use those spaces\n\n%><(<N>), %><|(<N>)\nsimilar to %<(<N>), %<|(<N>) respectively, but padding both sides (i.e. the text\nis centered)\n\n• Placeholders that expand to information extracted from the commit:\n\n%H\ncommit hash\n\n%h\nabbreviated commit hash\n\n%T\ntree hash\n\n%t\nabbreviated tree hash\n\n%P\nparent hashes\n\n%p\nabbreviated parent hashes\n\n%an\nauthor name\n\n%aN\nauthor name (respecting .mailmap, see git-shortlog(1) or git-blame(1))\n\n%ae\nauthor email\n\n%aE\nauthor email (respecting .mailmap, see git-shortlog(1) or git-blame(1))\n\n%al\nauthor email local-part (the part before the @ sign)\n\n%aL\nauthor local-part (see %al) respecting .mailmap, see git-shortlog(1) or git-\nblame(1))\n\n%ad\nauthor date (format respects --date= option)\n\n%aD\nauthor date, RFC2822 style\n\n%ar\nauthor date, relative\n\n%at\nauthor date, UNIX timestamp\n\n%ai\nauthor date, ISO 8601-like format\n\n%aI\nauthor date, strict ISO 8601 format\n\n%as\nauthor date, short format (YYYY-MM-DD)\n\n%ah\nauthor date, human style (like the --date=human option of git-rev-list(1))\n\n%cn\ncommitter name\n\n%cN\ncommitter name (respecting .mailmap, see git-shortlog(1) or git-blame(1))\n\n%ce\ncommitter email\n\n%cE\ncommitter email (respecting .mailmap, see git-shortlog(1) or git-blame(1))\n\n%cl\ncommitter email local-part (the part before the @ sign)\n\n%cL\ncommitter local-part (see %cl) respecting .mailmap, see git-shortlog(1) or git-\nblame(1))\n\n%cd\ncommitter date (format respects --date= option)\n\n%cD\ncommitter date, RFC2822 style\n\n%cr\ncommitter date, relative\n\n%ct\ncommitter date, UNIX timestamp\n\n%ci\ncommitter date, ISO 8601-like format\n\n%cI\ncommitter date, strict ISO 8601 format\n\n%cs\ncommitter date, short format (YYYY-MM-DD)\n\n%ch\ncommitter date, human style (like the --date=human option of git-rev-list(1))\n\n%d\nref names, like the --decorate option of git-log(1)\n\n%D\nref names without the \" (\", \")\" wrapping.\n\n%(describe[:options])\nhuman-readable name, like git-describe(1); empty string for undescribable\ncommits. The describe string may be followed by a colon and zero or more\ncomma-separated options. Descriptions can be inconsistent when tags are added or\nremoved at the same time.\n\n• match=<pattern>: Only consider tags matching the given glob(7) pattern,\nexcluding the \"refs/tags/\" prefix.\n\n• exclude=<pattern>: Do not consider tags matching the given glob(7) pattern,\nexcluding the \"refs/tags/\" prefix.\n\n%S\nref name given on the command line by which the commit was reached (like git log\n--source), only works with git log\n\n%e\nencoding\n\n%s\nsubject\n\n%f\nsanitized subject line, suitable for a filename\n\n%b\nbody\n\n%B\nraw body (unwrapped subject and body)\n\n%GG\nraw verification message from GPG for a signed commit\n\n%G?\nshow \"G\" for a good (valid) signature, \"B\" for a bad signature, \"U\" for a good\nsignature with unknown validity, \"X\" for a good signature that has expired, \"Y\"\nfor a good signature made by an expired key, \"R\" for a good signature made by a\nrevoked key, \"E\" if the signature cannot be checked (e.g. missing key) and \"N\"\nfor no signature\n\n%GS\nshow the name of the signer for a signed commit\n\n%GK\nshow the key used to sign a signed commit\n\n%GF\nshow the fingerprint of the key used to sign a signed commit\n\n%GP\nshow the fingerprint of the primary key whose subkey was used to sign a signed\ncommit\n\n%GT\nshow the trust level for the key used to sign a signed commit\n\n%gD\nreflog selector, e.g., refs/stash@{1} or refs/stash@{2 minutes ago}; the format\nfollows the rules described for the -g option. The portion before the @ is the\nrefname as given on the command line (so git log -g refs/heads/master would yield\nrefs/heads/master@{0}).\n\n%gd\nshortened reflog selector; same as %gD, but the refname portion is shortened for\nhuman readability (so refs/heads/master becomes just master).\n\n%gn\nreflog identity name\n\n%gN\nreflog identity name (respecting .mailmap, see git-shortlog(1) or git-blame(1))\n\n%ge\nreflog identity email\n\n%gE\nreflog identity email (respecting .mailmap, see git-shortlog(1) or git-blame(1))\n\n%gs\nreflog subject\n\n%(trailers[:options])\ndisplay the trailers of the body as interpreted by git-interpret-trailers(1). The\ntrailers string may be followed by a colon and zero or more comma-separated\noptions. If any option is provided multiple times the last occurrence wins.\n\nThe boolean options accept an optional value [=<BOOL>]. The values true, false,\non, off etc. are all accepted. See the \"boolean\" sub-section in \"EXAMPLES\" in\ngit-config(1). If a boolean option is given with no value, it’s enabled.\n\n• key=<K>: only show trailers with specified key. Matching is done\ncase-insensitively and trailing colon is optional. If option is given\nmultiple times trailer lines matching any of the keys are shown. This option\nautomatically enables the only option so that non-trailer lines in the\ntrailer block are hidden. If that is not desired it can be disabled with\nonly=false. E.g., %(trailers:key=Reviewed-by) shows trailer lines with key\nReviewed-by.\n\n• only[=<BOOL>]: select whether non-trailer lines from the trailer block should\nbe included.\n\n• separator=<SEP>: specify a separator inserted between trailer lines. When\nthis option is not given each trailer line is terminated with a line feed\ncharacter. The string SEP may contain the literal formatting codes described\nabove. To use comma as separator one must use %x2C as it would otherwise be\nparsed as next option. E.g., %(trailers:key=Ticket,separator=%x2C ) shows all\ntrailer lines whose key is \"Ticket\" separated by a comma and a space.\n\n• unfold[=<BOOL>]: make it behave as if interpret-trailer’s --unfold option was\ngiven. E.g., %(trailers:only,unfold=true) unfolds and shows all trailer\nlines.\n\n• keyonly[=<BOOL>]: only show the key part of the trailer.\n\n• valueonly[=<BOOL>]: only show the value part of the trailer.\n\n• keyvalueseparator=<SEP>: specify a separator inserted between trailer\nlines. When this option is not given each trailer key-value pair is separated\nby \": \". Otherwise it shares the same semantics as separator=<SEP> above.\n\nNote\nSome placeholders may depend on other options given to the revision traversal engine. For\nexample, the %g* reflog options will insert an empty string unless we are traversing\nreflog entries (e.g., by git log -g). The %d and %D placeholders will use the \"short\"\ndecoration format if --decorate was not already provided on the command line.\n\nIf you add a + (plus sign) after % of a placeholder, a line-feed is inserted immediately\nbefore the expansion if and only if the placeholder expands to a non-empty string.\n\nIf you add a - (minus sign) after % of a placeholder, all consecutive line-feeds immediately\npreceding the expansion are deleted if and only if the placeholder expands to an empty\nstring.\n\nIf you add a ` ` (space) after % of a placeholder, a space is inserted immediately before the\nexpansion if and only if the placeholder expands to a non-empty string.\n\n• tformat:\n\nThe tformat: format works exactly like format:, except that it provides \"terminator\"\nsemantics instead of \"separator\" semantics. In other words, each commit has the message\nterminator character (usually a newline) appended, rather than a separator placed between\nentries. This means that the final entry of a single-line format will be properly\nterminated with a new line, just as the \"oneline\" format does. For example:\n\n$ git log -2 --pretty=format:%h 4da45bef \\\n| perl -pe '$ .= \" -- NO NEWLINE\\n\" unless /\\n/'\n4da45be\n7134973 -- NO NEWLINE\n\n$ git log -2 --pretty=tformat:%h 4da45bef \\\n| perl -pe '$ .= \" -- NO NEWLINE\\n\" unless /\\n/'\n4da45be\n7134973\n\nIn addition, any unrecognized string that has a % in it is interpreted as if it has\ntformat: in front of it. For example, these two are equivalent:\n\n$ git log -2 --pretty=tformat:%h 4da45bef\n$ git log -2 --pretty=%h 4da45bef\n\n", "subsections": [] }, "EXAMPLES": { "content": "• Print the list of commits reachable from the current branch.\n\ngit rev-list HEAD\n\n\n• Print the list of commits on this branch, but not present in the upstream branch.\n\ngit rev-list @{upstream}..HEAD\n\n\n• Format commits with their author and commit message (see also the porcelain git-log(1)).\n\ngit rev-list --format=medium HEAD\n\n\n• Format commits along with their diffs (see also the porcelain git-log(1), which can do\nthis in a single process).\n\ngit rev-list HEAD |\ngit diff-tree --stdin --format=medium -p\n\n\n• Print the list of commits on the current branch that touched any file in the\nDocumentation directory.\n\ngit rev-list HEAD -- Documentation/\n\n\n• Print the list of commits authored by you in the past year, on any branch, tag, or other\nref.\n\ngit rev-list --author=you@example.com --since=1.year.ago --all\n\n\n• Print the list of objects reachable from the current branch (i.e., all commits and the\nblobs and trees they contain).\n\ngit rev-list --objects HEAD\n\n\n• Compare the disk size of all reachable objects, versus those reachable from reflogs,\nversus the total packed size. This can tell you whether running git repack -ad might\nreduce the repository size (by dropping unreachable objects), and whether expiring\nreflogs might help.\n\n# reachable objects\ngit rev-list --disk-usage --objects --all\n# plus reflogs\ngit rev-list --disk-usage --objects --all --reflog\n# total disk size used\ndu -c .git/objects/pack/*.pack .git/objects/??/*\n# alternative to du: add up \"size\" and \"size-pack\" fields\ngit count-objects -v\n\n\n• Report the disk size of each branch, not including objects used by the current branch.\nThis can find outliers that are contributing to a bloated repository size (e.g., because\nsomebody accidentally committed large build artifacts).\n\ngit for-each-ref --format='%(refname)' |\nwhile read branch\ndo\nsize=$(git rev-list --disk-usage --objects HEAD..$branch)\necho \"$size $branch\"\ndone |\nsort -n\n\n\n• Compare the on-disk size of branches in one group of refs, excluding another. If you\nco-mingle objects from multiple remotes in a single repository, this can show which\nremotes are contributing to the repository size (taking the size of origin as a\nbaseline).\n\ngit rev-list --disk-usage --objects --remotes=$suspect --not --remotes=origin\n\n", "subsections": [] }, "GIT": { "content": "Part of the git(1) suite\n\n\n\nGit 2.34.1 02/26/2026 GIT-REV-LIST(1)", "subsections": [] } } } }