doc: commit: synchronize <pathspec> description
`git add` shows an example of good writing, follow it. This also better disambiguates <file>... header. Signed-off-by: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Alexandr Miloslavskiy committed
Nov 19, 2019 at 16:48 UTC
66a25a7242e4e16480eab89da6557f90a2924c12
1 file changed
+8
-7
Documentation/git-commit.txt
+8
-7
@@ -13,7 +13,7 @@ SYNOPSIS
13
[-F <file> | -m <msg>] [--reset-author] [--allow-empty]
14
[--allow-empty-message] [--no-verify] [-e] [--author=<author>]
15
[--date=<date>] [--cleanup=<mode>] [--[no-]status]
16
- [-i | -o] [-S[<keyid>]] [--] [<file>...]
16
+ [-i | -o] [-S[<keyid>]] [--] [<pathspec>...]
17
18
DESCRIPTION
19
-----------
@@ -345,12 +345,13 @@ changes to tracked files.
345
\--::
346
Do not interpret any more arguments as options.
347
348
-<file>...::
349
- When files are given on the command line, the command
350
- commits the contents of the named files, without
351
- recording the changes already staged. The contents of
352
- these files are also staged for the next commit on top
353
- of what have been staged before.
348
+<pathspec>...::
349
+ When pathspec is given on the command line, commit the contents of
350
+ the files that match the pathspec without recording the changes
351
+ already added to the index. The contents of these files are also
352
+ staged for the next commit on top of what have been staged before.
353
++
354
+For more details, see the 'pathspec' entry in linkgit:gitglossary[7].
355
356
:git-commit: 1
357
include::date-formats.txt[]