* [PATCH] Elaborate on why ':' is a bad idea in a ref name.
@ 2006-05-21 2:03 Shawn Pearce
0 siblings, 0 replies; only message in thread
From: Shawn Pearce @ 2006-05-21 2:03 UTC (permalink / raw)
To: junio; +Cc: git
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
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
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2006-05-21 2:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-21 2:03 [PATCH] Elaborate on why ':' is a bad idea in a ref name Shawn Pearce
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox