range-diff(docs): explain how to specify commit ranges
There are three forms, depending whether the user specifies one, two or three non-option arguments. We've never actually explained how this works in the manual, so let's explain it. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Feb 5, 2021 at 14:44 UTC
2cc543deab38c188906c41e537dc5c7de98b93d7
1 file changed
+11
Documentation/git-range-diff.txt
+11
@@ -28,6 +28,17 @@ Finally, the list of matching commits is shown in the order of the
28
second commit range, with unmatched commits being inserted just after
29
all of their ancestors have been shown.
30
31
+There are three ways to specify the commit ranges:
32
+
33
+- `<range1> <range2>`: Either commit range can be of the form
34
+ `<base>..<rev>`, `<rev>^!` or `<rev>^-<n>`. See `SPECIFYING RANGES`
35
+ in linkgit:gitrevisions[7] for more details.
36
+
37
+- `<rev1>...<rev2>`. This is equivalent to
38
+ `<rev2>..<rev1> <rev1>..<rev2>`.
39
+
40
+- `<base> <rev1> <rev2>`: This is equivalent to `<base>..<rev1>
41
+ <base>..<rev2>`.
42
43
OPTIONS
44
-------