Skip to content

Commit 2b68222

Browse files
peffgitster
authored andcommitted
doc/rev-list-options: clarify "commit@{Nth}" for "-g" option
When "log -g" shows "HEAD@{1}", "HEAD@{2}", etc, calling that "commit@{Nth}" is not really accurate. The "HEAD" part is really the refname. By saying "commit", a reader may misunderstand that to mean something related to the specific commit we are showing, not the ref whose reflog we are traversing. While we're here, let's also switch these instances to use literal backticks, as our style guide recommends. As a bonus, that lets us drop some asciidoc quoting. Signed-off-by: Jeff King <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent e634160 commit 2b68222

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/rev-list-options.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -252,9 +252,9 @@ list.
252252
+
253253
With `--pretty` format other than `oneline` (for obvious reasons),
254254
this causes the output to have two extra lines of information
255-
taken from the reflog. By default, 'commit@\{Nth}' notation is
255+
taken from the reflog. By default, `ref@{Nth}` notation is
256256
used in the output. When the starting commit is specified as
257-
'commit@\{now}', output also uses 'commit@\{timestamp}' notation
257+
`ref@{now}`, output also uses `ref@{timestamp}` notation
258258
instead. Under `--pretty=oneline`, the commit message is
259259
prefixed with this information on the same line.
260260
This option cannot be combined with `--reverse`.

0 commit comments

Comments
 (0)