gitignore.txt: elaborate shell glob syntax
`fnmatch(3)` is a great mention if the intended audience is programmers. For normal users it's probably better to spell out what a shell glob is. This paragraph is updated to roughly tell (or remind) what the main wildcards are supposed to do. All the details are still hidden away behind the `fnmatch(3)` wall because bringing the whole specification here may be too much. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Duy Nguyen committed
Feb 1, 2018 at 16:59 UTC
2e22a85e5c01d041434682fe75f58be94de0801b
1 file changed
+5
-6
Documentation/gitignore.txt
+5
-6
@@ -102,12 +102,11 @@ PATTERN FORMAT
102
(relative to the toplevel of the work tree if not from a
103
`.gitignore` file).
104
105
- - Otherwise, Git treats the pattern as a shell glob suitable
106
- for consumption by fnmatch(3) with the FNM_PATHNAME flag:
107
- wildcards in the pattern will not match a / in the pathname.
108
- For example, "Documentation/{asterisk}.html" matches
109
- "Documentation/git.html" but not "Documentation/ppc/ppc.html"
110
- or "tools/perf/Documentation/perf.html".
105
+ - Otherwise, Git treats the pattern as a shell glob: "`*`" matches
106
+ anything except "`/`", "`?`" matches any one character except "`/`"
107
+ and "`[]`" matches one character in a selected range. See
108
+ fnmatch(3) and the FNM_PATHNAME flag for a more detailed
109
+ description.
110
111
- A leading slash matches the beginning of the pathname.
112
For example, "/{asterisk}.c" matches "cat-file.c" but not