path: root/Documentation/git-check-ref-format.txt
diff options
authorJunio C Hamano <>2005-12-16 02:03:59 (GMT)
committerJunio C Hamano <>2005-12-17 02:23:52 (GMT)
commit68283999f8ae0e9286f8b7f199905b77d608cb80 (patch)
tree191914d18206d0b668db19685e27343ba6f599e6 /Documentation/git-check-ref-format.txt
parent3ae854c3567dd10055fbe12b8bd91bd2d447f55f (diff)
Forbid pattern maching characters in refnames.
by marking '?', '*', and '[' as bad_ref_char(). Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-check-ref-format.txt')
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index 636e951..f7f84c6 100644
--- a/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@ -26,13 +26,15 @@ imposes the following rules on how refs are named:
. It cannot have ASCII control character (i.e. bytes whose
values are lower than \040, or \177 `DEL`), space, tilde `~`,
- caret `{caret}`, or colon `:` anywhere;
+ caret `{caret}`, colon `:`, question-mark `?`, asterisk `*`,
+ or open bracket `[` anywhere;
. It cannot end with a slash `/`.
These rules makes it easy for shell script based tools to parse
-refnames, and also avoids ambiguities in certain refname
-expressions (see gitlink:git-rev-parse[1]). Namely:
+refnames, pathname expansion by the shell when a refname is used
+unquoted (by mistake), and also avoids ambiguities in certain
+refname expressions (see gitlink:git-rev-parse[1]). Namely:
. double-dot `..` are often used as in `ref1..ref2`, and in some
context this notation means `{caret}ref1 ref2` (i.e. not in