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>
Shawn Pearce committed
May 20, 2006 at 21:54 UTC
2b1f4247ab5881cfde1d35ca3e3c48b7de8f449c
2 files changed
+7
-1
Documentation/git-branch.txt
+3
@@ -43,6 +43,9 @@ OPTIONS
43
44
<branchname>::
45
The name of the branch to create or delete.
46
+ The new branch name must pass all checks defined by
47
+ gitlink:git-check-ref-format[1]. Some of these checks
48
+ may restrict the characters allowed in a branch name.
49
50
<start-point>::
51
The new branch will be created with a HEAD equal to this. It may
Documentation/git-checkout.txt
+4
-1
@@ -35,7 +35,10 @@ OPTIONS
35
Force a re-read of everything.
36
37
-b::
38
- Create a new branch and start it at <branch>.
38
+ Create a new branch named <new_branch> and start it at
39
+ <branch>. The new branch name must pass all checks defined
40
+ by gitlink:git-check-ref-format[1]. Some of these checks
41
+ may restrict the characters allowed in a branch name.
42
43
-m::
44
If you have local modifications to one or more files that