diff options
| author | Junio C Hamano <junio@kernel.org> | 2010-10-14 04:37:28 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@kernel.org> | 2010-10-14 04:37:28 +0000 |
| commit | c27b733bfcf3bef4722ef8d46334aff3e15e0cd2 (patch) | |
| tree | 1a666e343738a0601732529bb7e0dc1be6775f96 /git-check-ref-format.txt | |
| parent | 657fd8a8dd93c9d5c7534016aa6601c564fe2601 (diff) | |
| download | git-htmldocs-c27b733bfcf3bef4722ef8d46334aff3e15e0cd2.tar.gz | |
Autogenerated HTML docs for v1.7.3.1-120-g38a18
Diffstat (limited to 'git-check-ref-format.txt')
| -rw-r--r-- | git-check-ref-format.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/git-check-ref-format.txt b/git-check-ref-format.txt index f5c2e0601..205d83dd0 100644 --- a/git-check-ref-format.txt +++ b/git-check-ref-format.txt @@ -49,7 +49,7 @@ git imposes the following rules on how references are named: These rules make it easy for shell script based tools to parse reference names, pathname expansion by the shell when a reference name is used unquoted (by mistake), and also avoids ambiguities in certain -reference name expressions (see linkgit:gitrevisions[1]): +reference name expressions (see linkgit:gitrevisions[7]): . A double-dot `..` is often used as in `ref1..ref2`, and in some contexts this notation means `{caret}ref1 ref2` (i.e. not in |