[PATCH] Elaborate on why ':' is a bad idea in a ref name.

Shawn Pearce· May 21, 2006, 02:03 UTC · lore

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>

---

0b552e48ed1d1ce01e0c2850e90caad8150c199c
 Documentation/git-check-ref-format.txt |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

0b552e48ed1d1ce01e0c2850e90caad8150c199c

Show changes to Documentation/git-check-ref-format.txt +2 −0

diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index 7dc1bdb..3ea720d 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
 
 . 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

-- 
1.3.3.gfad60

patchElaborate on why ':' is a bad idea in a ref name.