freshlybakedca.ke / git
Git fork
fork atom

doc: correct doc for glob pathspec

gitglossary documents Git pathspecs. One type of pathspec is the "glob"
pathspec, prefixed with the magic word "glob".

Regarding glob pathspecs, gitglossary says, '"**/foo" matches file or
directory "foo" anywhere, the same as pattern "foo".' That last phrase
('the same as pattern "foo") is incorrect. "**/foo" and "foo" are not
equivalent. "**/foo" matches foo anywhere, but "foo" does not.

This change removes the incorrect phrase from the glob pathspec doc.

Signed-off-by: Russell Hanneken <rhanneken@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

authored by

Russell Hanneken and committed by
Junio C Hamano f4fa8a36 f368df43

+2 -3
unified split
+2 -3
Documentation/glossary-content.adoc
··· 418 419 - A leading "`**`" followed by a slash means match in all 420 directories. For example, "`**/foo`" matches file or directory 421 - "`foo`" anywhere, the same as pattern "`foo`". "`**/foo/bar`" 422 - matches file or directory "`bar`" anywhere that is directly 423 - under directory "`foo`". 424 425 - A trailing "`/**`" matches everything inside. For example, 426 "`abc/**`" matches all files inside directory "abc", relative
··· 418 419 - A leading "`**`" followed by a slash means match in all 420 directories. For example, "`**/foo`" matches file or directory 421 + "`foo`" anywhere. "`**/foo/bar`" matches file or directory "`bar`" 422 + anywhere that is directly under directory "`foo`". 423 424 - A trailing "`/**`" matches everything inside. For example, 425 "`abc/**`" matches all files inside directory "abc", relative