summaryrefslogtreecommitdiff
path: root/Documentation/git-lost-found.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-08-06 20:36:47 (GMT)
committerJunio C Hamano <gitster@pobox.com>2012-08-06 21:04:16 (GMT)
commit831e61f80fab2d3f9ba1773e657803dcf8b16432 (patch)
tree6ced3d26ab664b5ab3885eaef205e8e0d229c5bf /Documentation/git-lost-found.txt
parentd0f1ea6003d97e63110fa7d50bb07f546a909b6e (diff)
downloadgit-831e61f80fab2d3f9ba1773e657803dcf8b16432.zip
git-831e61f80fab2d3f9ba1773e657803dcf8b16432.tar.gz
git-831e61f80fab2d3f9ba1773e657803dcf8b16432.tar.bz2
Documentation: do not mention .git/refs/* directories
It is an implementation detail that a new tag is created by adding a file in the .git/refs/tags directory. The only thing the user needs to know is that a "git tag" creates a ref in the refs/tags namespace, and without "-f", it does not overwrite an existing tag. Inspired by a report from 乙酸鋰 <ch3cooli@gmail.com>; I think I caught all the existing mention in Documentation/ directory in the tip of 1.7.9.X maintenance track, but we may have added new ones since then. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-lost-found.txt')
-rw-r--r--Documentation/git-lost-found.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/git-lost-found.txt b/Documentation/git-lost-found.txt
index c406a11..d549328 100644
--- a/Documentation/git-lost-found.txt
+++ b/Documentation/git-lost-found.txt
@@ -48,7 +48,8 @@ $ gitk $(cd .git/lost-found/commit && echo ??*)
------------
After making sure you know which the object is the tag you are looking
-for, you can reconnect it to your regular .git/refs hierarchy.
+for, you can reconnect it to your regular `refs` hierarchy by using
+the `update-ref` command.
------------
$ git cat-file -t 1ef2b196