summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 0065236)
raw | patch | inline | side by side (parent: 0065236)
author | Michael J Gruber <git@drmicha.warpmail.net> | |
Wed, 13 May 2009 15:43:06 +0000 (17:43 +0200) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 13 May 2009 20:12:22 +0000 (13:12 -0700) |
'git check-ref-format' checks for the presence of at least one '/', the
idea being that there should be no refs directly below 'refs/', so there
should be a category like 'heads/' or 'tags/' in a refname.
Try and make this clearer in the man page.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
idea being that there should be no refs directly below 'refs/', so there
should be a category like 'heads/' or 'tags/' in a refname.
Try and make this clearer in the man page.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-check-ref-format.txt | patch | blob | history |
index c1ce26884e73f1599602472ba5032988486cc465..0873e60f7f61f51143e88fd8637b34627620a7dd 100644 (file)
grouping, but no slash-separated component can begin with a
dot `.`.
+. They must contain at least one `/`. This enforces the presence of a
+ category like `heads/`, `tags/` etc. but the actual names are not
+ restricted.
+
. They cannot have two consecutive dots `..` anywhere.
. They cannot have ASCII control characters (i.e. bytes whose