From: "Jakub Narębski" <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Carlos Martín Nieto" <cmn@elego.de>
Subject: Re: [PATCH] glossary: extend "detached HEAD" description
Date: Wed, 10 Apr 2013 14:59:40 +0200 [thread overview]
Message-ID: <5165623C.703@gmail.com> (raw)
In-Reply-To: <7vwqshc8ec.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> index f928b57..69c90d1 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -100,9 +100,22 @@ to point at the new commit.
>
> [[def_detached_HEAD]]detached HEAD::
> Normally the <<def_HEAD,HEAD>> stores the name of a
> - <<def_branch,branch>>. However, git also allows you to <<def_checkout,check out>>
> - an arbitrary <<def_commit,commit>> that isn't necessarily the tip of any
> - particular branch. In this case HEAD is said to be "detached".
> + <<def_branch,branch>>, and commands that operate on the
> + history HEAD represents operate on the history leading to the
> + tip of the branch the HEAD points at. However, Git also
> + allows you to <<def_checkout,check out>> an arbitrary
> + <<def_commit,commit>> that isn't necessarily the tip of any
> + particular branch. The HEAD in such a state is called
> + "detached".
Should we also add that "git branch" output shows this situation
as "(no branch)"?
Nb. this is not documented in git-branch(1) manpage either...
--
Jakub Narębski
next prev parent reply other threads:[~2013-04-10 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 15:19 [PATCH] glossary: extend "detached HEAD" description Junio C Hamano
2013-04-05 23:46 ` Eric Sunshine
2013-04-10 12:59 ` Jakub Narębski [this message]
2013-04-10 14:45 ` Junio C Hamano
2013-04-10 18:29 ` Jakub Narębski
2013-04-10 19:35 ` 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=5165623C.703@gmail.com \
--to=jnareb@gmail.com \
--cc=cmn@elego.de \
--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).