aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShawn Pearce <spearce@spearce.org>2006-05-20 22:03:14 -0400
committerJunio C Hamano <junkio@cox.net>2006-05-21 02:07:43 -0700
commit87a56cd3b1dfb651076fbdc6d3591a32d1286a03 (patch)
treef8d05ed8dc67e42cdc4fc2c49bcf6c6f36357258
parent2b1f4247ab5881cfde1d35ca3e3c48b7de8f449c (diff)
downloadgit-87a56cd3b1dfb651076fbdc6d3591a32d1286a03.tar.gz
git-87a56cd3b1dfb651076fbdc6d3591a32d1286a03.tar.xz
Elaborate on why ':' is a bad idea in a ref name.
With the new cat-file syntax of 'v1.3.3:refs.c' we should mention it as part of the reason why ':' is not permitted in a ref name. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/git-check-ref-format.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index 7dc1bdb6e..3ea720dd0 100644
--- a/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@ -45,6 +45,8 @@ refname expressions (see gitlink:git-rev-parse[1]). Namely:
. colon `:` is used as in `srcref:dstref` to mean "use srcref\'s
value and store it in dstref" in fetch and push operations.
+ It may also be used to select a specific object such as with
+ gitlink:git-cat-file[1] "git-cat-file blob v1.3.3:refs.c".
GIT