Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Elaborate on why ':' is a bad idea in a ref name.
author
Shawn Pearce
<spearce@spearce.org>
Sun, 21 May 2006 02:03:14 +0000
(22:03 -0400)
committer
Junio C Hamano
<junkio@cox.net>
Sun, 21 May 2006 09:07:43 +0000
(
02:07
-0700)
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>
Documentation/git-check-ref-format.txt
patch
|
blob
|
history
raw
|
patch
| inline |
side by side
(parent:
2b1f424
)
diff --git
a/Documentation/git-check-ref-format.txt
b/Documentation/git-check-ref-format.txt
index 7dc1bdb6ef62f1325f8cf0567aa65c56728522ec..3ea720dd005f7a9b4a66a419cf5438a3a7d0fa8b 100644
(file)
--- 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