diff options
author | Junio C Hamano <gitster@pobox.com> | 2017-11-10 15:01:12 +0900 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-11-10 15:01:12 +0900 |
commit | 3a9c034734bf5aa3e3b139e72a6b0b96ddf0b3e9 (patch) | |
tree | 53a0176d8d930235e125d80c7705681f80bf1957 /git-check-ref-format.txt | |
parent | a65b67605da51cd9b94659acdac8984dd205dcc7 (diff) | |
download | git-htmldocs-3a9c034734bf5aa3e3b139e72a6b0b96ddf0b3e9.tar.gz |
Autogenerated HTML docs for v2.15.0-164-g4123b
Diffstat (limited to 'git-check-ref-format.txt')
-rw-r--r-- | git-check-ref-format.txt | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/git-check-ref-format.txt b/git-check-ref-format.txt index 92777cef2..cf0a0b7df 100644 --- a/git-check-ref-format.txt +++ b/git-check-ref-format.txt @@ -77,7 +77,14 @@ reference name expressions (see linkgit:gitrevisions[7]): . at-open-brace `@{` is used as a notation to access a reflog entry. -With the `--branch` option, it expands the ``previous branch syntax'' +With the `--branch` option, the command takes a name and checks if +it can be used as a valid branch name (e.g. when creating a new +branch). The rule `git check-ref-format --branch $name` implements +may be stricter than what `git check-ref-format refs/heads/$name` +says (e.g. a dash may appear at the beginning of a ref component, +but it is explicitly forbidden at the beginning of a branch name). +When run with `--branch` option in a repository, the input is first +expanded for the ``previous branch syntax'' `@{-n}`. For example, `@{-1}` is a way to refer the last branch you were on. This option should be used by porcelains to accept this syntax anywhere a branch name is expected, so they can act as if you |