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 <gitster@pobox.com>
Junio C Hamano committed
Jun 23, 2011 at 09:38 UTC
487b04411d625ff912543e4313a3343db62429e4
1 file changed
+8
-8
Documentation/glossary-content.txt
+8
-8
@@ -427,14 +427,14 @@ including Documentation/chapter_1/figure_1.jpg.
427
command.
428
429
[[def_tag]]tag::
430
- A <<def_ref,ref>> pointing to a <<def_tag_object,tag>> or
431
- <<def_commit_object,commit object>>. In contrast to a <<def_head,head>>,
432
- a tag is not changed by a <<def_commit,commit>>. Tags (not
433
- <<def_tag_object,tag objects>>) are stored in `$GIT_DIR/refs/tags/`. A
434
- git tag has nothing to do with a Lisp tag (which would be
435
- called an <<def_object_type,object type>> in git's context). A
436
- tag is most typically used to mark a particular point in the
437
- commit ancestry <<def_chain,chain>>.
430
+ A <<def_ref,ref>> under `refs/tags/` namespace that points to an
431
+ object of an arbitrary type (typically a tag points to either a
432
+ <<def_tag_object,tag>> or a <<def_commit_object,commit object>>).
433
+ In contrast to a <<def_head,head>>, a tag is not updated by
434
+ the `commit` command. A git tag has nothing to do with a Lisp
435
+ tag (which would be called an <<def_object_type,object type>>
436
+ in git's context). A tag is most typically used to mark a particular
437
+ point in the commit ancestry <<def_chain,chain>>.
438
439
[[def_tag_object]]tag object::
440
An <<def_object,object>> containing a <<def_ref,ref>> pointing to