summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: deaef1e)
raw | patch | inline | side by side (parent: deaef1e)
author | Junio C Hamano <gitster@pobox.com> | |
Thu, 23 Jun 2011 16:48:49 +0000 (09:48 -0700) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Thu, 23 Jun 2011 22:39:28 +0000 (15:39 -0700) |
HEAD on a branch does reference a commit via the branch ref it refers to.
The main difference of a detached HEAD is that it _directly_ refers to
a commit. Clarify this.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The main difference of a detached HEAD is that it _directly_ refers to
a commit. Clarify this.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/glossary-content.txt | patch | blob | history |
index f4300684679c7a5ef06ae4cb7be7ff8ee64bb64c..f4fd5b046debb3e2236be4d00fdbb4eea73b7010 100644 (file)
working tree>> is normally derived from the state of the tree
referred to by HEAD. HEAD is a reference to one of the
<<def_head,heads>> in your repository, except when using a
- <<def_detached_HEAD,detached HEAD>>, in which case it may
- reference an arbitrary commit.
+ <<def_detached_HEAD,detached HEAD>>, in which case it directly
+ references an arbitrary commit.
[[def_head_ref]]head ref::
A synonym for <<def_head,head>>.