Skip to content

Commit d9a4937

Browse files
jnavilagitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 07583a2 commit d9a4937

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/rev-list-description.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ endif::git-log[]
2626
means "list all the commits which are reachable from 'foo' or 'bar', but
2727
not from 'baz'".
2828

29-
A special notation "'<commit1>'..'<commit2>'" can be used as a
30-
short-hand for "^'<commit1>' '<commit2>'". For example, either of
29+
A special notation "`<commit1>..<commit2>`" can be used as a
30+
short-hand for "`^<commit1> <commit2>`". For example, either of
3131
the following may be used interchangeably:
3232

3333
ifdef::git-rev-list[]
@@ -43,7 +43,7 @@ $ git log HEAD ^origin
4343
-----------------------------------------------------------------------
4444
endif::git-log[]
4545

46-
Another special notation is "'<commit1>'...'<commit2>'" which is useful
46+
Another special notation is "`<commit1>...<commit2>`" which is useful
4747
for merges. The resulting set of commits is the symmetric difference
4848
between the two operands. The following two commands are equivalent:
4949

0 commit comments

Comments
 (0)