Merge branch 'gp/describe-match-uses-glob-pattern'

The syntax of the pattern given to the "--match=<pattern>" argument
to "git describe" was not documented to be a glob.

* gp/describe-match-uses-glob-pattern:
describe: Document --match pattern format

diff --combined Documentation/git-describe.txt
index 32da244fd55db8f8e24ea64787b61930d67cfbda,711040d2f1b8537623f633c3d0207ef4e27e1877..3c81e85ec5cf1b3090a879d49ad2445176312872
--- 1/Documentation/git-describe.txt
--- 2/Documentation/git-describe.txt
+++ b/Documentation/git-describe.txt
@@@ -81,8 -81,9 +81,9 @@@ OPTION
        that points at object deadbee....).
  
  --match <pattern>::
-       Only consider tags matching the given pattern (can be used to avoid
-       leaking private tags made from the repository).
+       Only consider tags matching the given `glob(7)` pattern,
+       excluding the "refs/tags/" prefix.  This can be used to avoid
+       leaking private tags from the repository.
  
  --always::
        Show uniquely abbreviated commit object as fallback.
@@@ -131,7 -132,7 +132,7 @@@ closest tagname without any suffix
  
  Note that the suffix you get if you type these commands today may be
  longer than what Linus saw above when he ran these commands, as your
 -git repository may have new commits whose object names begin with
 +Git repository may have new commits whose object names begin with
  975b that did not exist back then, and "-g975b" suffix alone may not
  be sufficient to disambiguate these commits.