From: Junio C Hamano Date: Thu, 23 Jun 2011 16:38:48 +0000 (-0700) Subject: glossary: update description of "tag" X-Git-Tag: v1.7.6.1~41^2~2 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=487b04411d625ff912543e4313a3343db62429e4;p=git.git glossary: update description of "tag" It is an unimportant implementation detail that ref namespaces are implemented as subdirectories of $GIT_DIR/refs. What is more important is that tags are in refs/tags hierarchy in the ref namespace. Also note that a tag can point at an object of arbitrary type, not limited to commit. Signed-off-by: Junio C Hamano --- diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt index 33716a31d..878de2115 100644 --- a/Documentation/glossary-content.txt +++ b/Documentation/glossary-content.txt @@ -427,14 +427,14 @@ including Documentation/chapter_1/figure_1.jpg. command. [[def_tag]]tag:: - A <> pointing to a <> or - <>. In contrast to a <>, - a tag is not changed by a <>. Tags (not - <>) are stored in `$GIT_DIR/refs/tags/`. A - git tag has nothing to do with a Lisp tag (which would be - called an <> in git's context). A - tag is most typically used to mark a particular point in the - commit ancestry <>. + A <> under `refs/tags/` namespace that points to an + object of an arbitrary type (typically a tag points to either a + <> or a <>). + In contrast to a <>, a tag is not updated by + the `commit` command. A git tag has nothing to do with a Lisp + tag (which would be called an <> + in git's context). A tag is most typically used to mark a particular + point in the commit ancestry <>. [[def_tag_object]]tag object:: An <> containing a <> pointing to