From: "Carlos Martín Nieto" <carlos@cmartin.tk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/5] glossary: clarify description of HEAD
Date: Thu, 23 Jun 2011 19:06:58 +0200 [thread overview]
Message-ID: <20110623170658.GC3142@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <1308847958-3429-6-git-send-email-gitster@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-23 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 4:45 [PATCH] git-remote.txt: fix wrong remote refspec Namhyung Kim
2011-06-23 5:35 ` Junio C Hamano
2011-06-23 6:17 ` Namhyung Kim
2011-06-23 8:12 ` [PATCH v2] " Namhyung Kim
2011-06-23 15:33 ` [PATCH] " Junio C Hamano
2011-06-23 16:03 ` Namhyung Kim
2011-06-23 16:52 ` [PATCH 0/5] Clarify "refs" Junio C Hamano
2011-06-23 16:52 ` [PATCH 1/5] check-ref-format doc: de-emphasize the implementation detail of a ref Junio C Hamano
2011-06-23 22:14 ` Eric Sunshine
2011-06-23 16:52 ` [PATCH 2/5] git.txt: " Junio C Hamano
2011-06-23 16:52 ` [PATCH 3/5] glossary: update description of "tag" Junio C Hamano
2011-06-23 22:19 ` Eric Sunshine
2011-06-23 16:52 ` [PATCH 4/5] glossary: update description of head and ref Junio C Hamano
2011-06-23 16:52 ` [PATCH 5/5] glossary: clarify description of HEAD Junio C Hamano
2011-06-23 17:06 ` Carlos Martín Nieto [this message]
2011-06-23 17:12 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110623170658.GC3142@centaur.lab.cmartin.tk \
--to=carlos@cmartin.tk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).