undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'nd/glossary-content-pathspec-markup' into maint

Browse Source 
* nd/glossary-content-pathspec-markup:
  glossary-content.txt: fix documentation of "**" patterns
This commit is contained in:
Junio C Hamano 2013-12-17 11:36:54 -08:00
commit 212607494d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/glossary-content.txt
View File

@ -362,12 +362,12 @@ full pathname may have special meaning:
- A leading "`**`" followed by a slash means match in all - A leading "`**`" followed by a slash means match in all
directories. For example, "`**/foo`" matches file or directory directories. For example, "`**/foo`" matches file or directory
"`foo`" anywhere, the same as pattern "`foo`". "**/foo/bar" "`foo`" anywhere, the same as pattern "`foo`". "`**/foo/bar`"
matches file or directory "`bar`" anywhere that is directly matches file or directory "`bar`" anywhere that is directly
under directory "`foo`". under directory "`foo`".
- A trailing "/**" matches everything inside. For example, - A trailing "`/**`" matches everything inside. For example,
"abc/**" matches all files inside directory "abc", relative "`abc/**`" matches all files inside directory "abc", relative
to the location of the `.gitignore` file, with infinite depth. to the location of the `.gitignore` file, with infinite depth.
- A slash followed by two consecutive asterisks then a slash - A slash followed by two consecutive asterisks then a slash