Skip to content

Commit

Permalink
Reference git-check-ref-format in git-branch.
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Shawn Pearce authored and Junio C Hamano committed May 21, 2006
1 parent 8824689 commit 2b1f424
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 1 deletion.
3 changes: 3 additions & 0 deletions Documentation/git-branch.txt
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,9 @@ OPTIONS

<branchname>::
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>::
The new branch will be created with a HEAD equal to this. It may
Expand Down
5 changes: 4 additions & 1 deletion Documentation/git-checkout.txt
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,10 @@ OPTIONS
Force a re-read of everything.

-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::
If you have local modifications to one or more files that
Expand Down

0 comments on commit 2b1f424

Please sign in to comment.