Reference git-check-ref-format in git-branch.

Its nice to have git-check-ref-format actually get mentioned in
git-branch's documentation as the syntax of a ref name must conform
to what is described in git-check-ref-format.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
maint
Shawn Pearce 2006-05-20 21:54:46 -04:00 committed by Junio C Hamano
parent 8824689884
commit 2b1f4247ab
2 changed files with 7 additions and 1 deletions

View File

@ -43,6 +43,9 @@ OPTIONS


<branchname>:: <branchname>::
The name of the branch to create or delete. The name of the branch to create or delete.
The new branch name must pass all checks defined by
gitlink:git-check-ref-format[1]. Some of these checks
may restrict the characters allowed in a branch name.


<start-point>:: <start-point>::
The new branch will be created with a HEAD equal to this. It may The new branch will be created with a HEAD equal to this. It may

View File

@ -35,7 +35,10 @@ OPTIONS
Force a re-read of everything. Force a re-read of everything.


-b:: -b::
Create a new branch and start it at <branch>. Create a new branch named <new_branch> and start it at
<branch>. The new branch name must pass all checks defined
by gitlink:git-check-ref-format[1]. Some of these checks
may restrict the characters allowed in a branch name.


-m:: -m::
If you have local modifications to one or more files that If you have local modifications to one or more files that