freshlybakedca.ke
Git fork
doc: git-log convert rev-list-description to new doc format
Use `backticks` for commit ranges. The new rendering engine will apply
synopsis rules to these spans.
Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
authored by
Jean-Noël Avila
and committed by
Junio C Hamano
ffe24e00
026f2e3b
+3
-3
Documentation/rev-list-description.adoc
+3
-3
Documentation/rev-list-description.adoc
···
26
means "list all the commits which are reachable from 'foo' or 'bar', but
27
not from 'baz'".
28
29
-
A special notation "'<commit1>'..'<commit2>'" can be used as a
30
-
short-hand for "^'<commit1>' '<commit2>'". For example, either of
31
the following may be used interchangeably:
32
33
ifdef::git-rev-list[]
···
43
-----------------------------------------------------------------------
44
endif::git-log[]
45
46
-
Another special notation is "'<commit1>'...'<commit2>'" which is useful
47
for merges. The resulting set of commits is the symmetric difference
48
between the two operands. The following two commands are equivalent:
49
···
26
means "list all the commits which are reachable from 'foo' or 'bar', but
27
not from 'baz'".
28
29
+
A special notation "`<commit1>..<commit2>`" can be used as a
30
+
short-hand for "`^<commit1> <commit2>`". For example, either of
31
the following may be used interchangeably:
32
33
ifdef::git-rev-list[]
···
43
-----------------------------------------------------------------------
44
endif::git-log[]
45
46
+
Another special notation is "`<commit1>...<commit2>`" which is useful
47
for merges. The resulting set of commits is the symmetric difference
48
between the two operands. The following two commands are equivalent:
49