admin/git
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: git-log convert rev-list-description to new doc format

Browse Source 
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>
This commit is contained in:
Jean-Noël Avila
2025-07-07 18:53:25 +00:00
committed by Junio C Hamano
parent 026f2e3be2
commit ffe24e00a5
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/rev-list-description.adoc
View File

@@ -26,8 +26,8 @@ endif::git-log[]
means "list all the commits which are reachable from 'foo' or 'bar', but means "list all the commits which are reachable from 'foo' or 'bar', but
not from 'baz'". not from 'baz'".
A special notation "'<commit1>'..'<commit2>'" can be used as a A special notation "`<commit1>..<commit2>`" can be used as a
short-hand for "^'<commit1>' '<commit2>'". For example, either of short-hand for "`^<commit1> <commit2>`". For example, either of
the following may be used interchangeably: the following may be used interchangeably:
ifdef::git-rev-list[] ifdef::git-rev-list[]
@@ -43,7 +43,7 @@ $ git log HEAD ^origin
----------------------------------------------------------------------- -----------------------------------------------------------------------
endif::git-log[] endif::git-log[]
Another special notation is "'<commit1>'...'<commit2>'" which is useful Another special notation is "`<commit1>...<commit2>`" which is useful
for merges. The resulting set of commits is the symmetric difference for merges. The resulting set of commits is the symmetric difference
between the two operands. The following two commands are equivalent: between the two operands. The following two commands are equivalent: