@@ -11,7 +11,7 @@ SYNOPSIS
1111'git add' [-n] [-v] [--force | -f] [--interactive | -i] [--patch | -p]
1212 [--edit | -e] [--all | [--update | -u]] [--intent-to-add | -N]
1313 [--refresh] [--ignore-errors] [--ignore-missing] [--]
14- [<filepattern >...]
14+ [<pathspec >...]
1515
1616DESCRIPTION
1717-----------
@@ -49,7 +49,7 @@ commit.
4949
5050OPTIONS
5151-------
52- <filepattern >...::
52+ <pathspec >...::
5353 Files to add content from. Fileglobs (e.g. `*.c`) can
5454 be given to add all matching files. Also a
5555 leading directory name (e.g. `dir` to add `dir/file1`
@@ -100,21 +100,21 @@ apply to the index. See EDITING PATCHES below.
100100
101101-u::
102102--update::
103- Only match <filepattern > against already tracked files in
103+ Only match <pathspec > against already tracked files in
104104 the index rather than the working tree. That means that it
105105 will never stage new files, but that it will stage modified
106106 new contents of tracked files and that it will remove files
107107 from the index if the corresponding files in the working tree
108108 have been removed.
109109+
110- If no <filepattern > is given, the current version of Git defaults to
110+ If no <pathspec > is given, the current version of Git defaults to
111111"."; in other words, update all tracked files in the current directory
112112and its subdirectories. This default will change in a future version
113113of Git, hence the form without <filepattern> should not be used.
114114
115115-A::
116116--all::
117- Like `-u`, but match <filepattern > against files in the
117+ Like `-u`, but match <pathspec > against files in the
118118 working tree in addition to the index. That means that it
119119 will find new files as well as staging modified content and
120120 removing files that are no longer in the working tree.
0 commit comments