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

PATCH New Shawn Pearce 1 participant 1 message Jun 15, 2016 Documentation

Share & tools

Shawn Pearce

author

2016-06-15 22:42 UTC #0 lore raw

PATCH 1/1 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 <[email protected]>

---

0b552e48ed1d1ce01e0c2850e90caad8150c199c

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

0b552e48ed1d1ce01e0c2850e90caad8150c199c

Documentation/git-check-ref-format.txt +2 -0

index 7dc1bdb..3ea720d 100644
@@ -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

Signature · 1 line

1.3.3.gfad60