diff options
author | Junio C Hamano <gitster@pobox.com> | 2021-02-22 16:57:12 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2021-02-22 16:57:12 -0800 |
commit | a70c988a0584e1197ffd19b26c28e9790da32363 (patch) | |
tree | eb0f2dd1584011f40e4589c81288ac3b9f3d7c61 /git-range-diff.txt | |
parent | b4fc8e8cbb4fa1443a8546bdff0b1e5cd06f15fd (diff) | |
download | git-htmldocs-a70c988a0584e1197ffd19b26c28e9790da32363.tar.gz |
Autogenerated HTML docs for v2.30.1-602-g966e6
Diffstat (limited to 'git-range-diff.txt')
-rw-r--r-- | git-range-diff.txt | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/git-range-diff.txt b/git-range-diff.txt index 9701c1e5f..fe350d7f4 100644 --- a/git-range-diff.txt +++ b/git-range-diff.txt @@ -10,6 +10,7 @@ SYNOPSIS [verse] 'git range-diff' [--color=[<when>]] [--no-color] [<diff-options>] [--no-dual-color] [--creation-factor=<factor>] + [--left-only | --right-only] ( <range1> <range2> | <rev1>...<rev2> | <base> <rev1> <rev2> ) DESCRIPTION @@ -28,6 +29,17 @@ Finally, the list of matching commits is shown in the order of the second commit range, with unmatched commits being inserted just after all of their ancestors have been shown. +There are three ways to specify the commit ranges: + +- `<range1> <range2>`: Either commit range can be of the form + `<base>..<rev>`, `<rev>^!` or `<rev>^-<n>`. See `SPECIFYING RANGES` + in linkgit:gitrevisions[7] for more details. + +- `<rev1>...<rev2>`. This is equivalent to + `<rev2>..<rev1> <rev1>..<rev2>`. + +- `<base> <rev1> <rev2>`: This is equivalent to `<base>..<rev1> + <base>..<rev2>`. OPTIONS ------- @@ -57,6 +69,14 @@ to revert to color all lines according to the outer diff markers See the ``Algorithm`` section below for an explanation why this is needed. +--left-only:: + Suppress commits that are missing from the first specified range + (or the "left range" when using the `<rev1>...<rev2>` format). + +--right-only:: + Suppress commits that are missing from the second specified range + (or the "right range" when using the `<rev1>...<rev2>` format). + --[no-]notes[=<ref>]:: This flag is passed to the `git log` program (see linkgit:git-log[1]) that generates the patches. |