From: Junio C Hamano <gitster@pobox.com>
To: "Carlos Martín Nieto" <carlos@cmartin.tk>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 5/5] glossary: clarify description of HEAD
Date: Thu, 23 Jun 2011 10:12:51 -0700 [thread overview]
Message-ID: <7vtybg320c.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110623170658.GC3142@centaur.lab.cmartin.tk> ("Carlos Martín Nieto"'s message of "Thu, 23 Jun 2011 19:06:58 +0200")
Carlos Martín Nieto <carlos@cmartin.tk> writes:
>> - <<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
True; I just kept the original without thinking too deeply about it.
prev parent reply other threads:[~2011-06-23 17:12 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
2011-06-23 17:12 ` Junio C Hamano [this message]
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=7vtybg320c.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=carlos@cmartin.tk \
--cc=git@vger.kernel.org \
/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).