From: "Dilip M" <dilipm79@gmail.com>
To: "Sitaram Chamarty" <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: user manual question
Date: Sun, 28 Dec 2008 22:06:56 +0530 [thread overview]
Message-ID: <c94f8e120812280836j4acab974s5139167ac6be54ee@mail.gmail.com> (raw)
In-Reply-To: <slrnglf3qh.c7j.sitaramc@sitaramc.homelinux.net>
On Sun, Dec 28, 2008 at 8:08 PM, <sitaramc@gmail.com> wrote:
> On 2008-12-28, Zorba <cr@altmore.co.uk> wrote:
>> Under "Examining an old version without creating a new branch"
>> subsection in chapter1
>>
>> to aid my understanding, could the statement:
>>
>> "The HEAD then refers to the SHA1 of the commit instead of to a
>> branch, and git branch shows that you are no longer on a branch:"
>>
>> be restated more explicitly as:
>>
>> "The HEAD then refers to the SHA1 of the commit instead of to a
>> branch head, and git branch shows that you are no longer on a branch
>> head:"
>
> Sure, but I prefer "tip"; reduces confusion between "head" and "HEAD"
> in spoken descriptions (I teach internal classes on git occasionally,
> once even on a conf call!)
+1
I was (am) was initially confused about head and HEAD and assumed that
they are both same.
-- dm
next prev parent reply other threads:[~2008-12-28 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 11:07 user manual question Zorba
2008-12-28 14:38 ` Sitaram Chamarty
2008-12-28 16:36 ` Dilip M [this message]
2008-12-29 0:51 ` Zorba
2008-12-29 0:48 ` Zorba
2008-12-29 1:12 ` Sitaram Chamarty
2008-12-29 6:33 ` Dilip M
2008-12-29 16:38 ` Zorba
2008-12-29 17:18 ` Björn Steinbrink
2008-12-29 17:20 ` Markus Heidelberg
2008-12-29 17:27 ` Sitaram Chamarty
2008-12-29 19:30 ` Daniel Barkalow
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=c94f8e120812280836j4acab974s5139167ac6be54ee@mail.gmail.com \
--to=dilipm79@gmail.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.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).