From: Carlos Martín Nieto <carlos@cmartin.tk>
Date: Thu, 23 Jun 2011 17:06:58 GMT
Subject: Re: [PATCH 5/5] glossary: clarify description of HEAD
Message-ID: <20110623170658.GC3142@centaur.lab.cmartin.tk>
In-Reply-To: <1308847958-3429-6-git-send-email-gitster@pobox.com>

On Thu, Jun 23, 2011 at 09:52:38AM -0700, Junio C Hamano wrote:
> 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>
> ---
>  Documentation/glossary-content.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> index dd690bd..f79da21 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -170,7 +170,7 @@ to point at the new commit.
>  	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
> +	<<def_detached_HEAD,detached HEAD>>, in which case it may directly

Why "may"? As I understand it, in detached HEAD, it /does/ point
directly to a commit

>  	reference an arbitrary commit.
>  
>  [[def_head_ref]]head ref::

Cheers,
   cmn
-- 
Carlos Martín Nieto | http://cmartin.tk

"¿Cómo voy a decir bobadas si soy mudo?" -- CACHAI