From: "Zorba" <cr@altmore.co.uk>
To: git@vger.kernel.org
Subject: Re: user manual question
Date: Mon, 29 Dec 2008 00:48:37 -0000 [thread overview]
Message-ID: <gj96pl$885$4@ger.gmane.org> (raw)
In-Reply-To: slrnglf3qh.c7j.sitaramc@sitaramc.homelinux.net
Hi Sitaram!
Thanks for clearing that one up.
Also, I did wonder about HEAD and head. One can move, the other doesn't!
(well, acually it does - head moves "forward", as the tip of the branch
grows)
you gotta love it
:-)
Thanks for your other post/reply too - I will be getting back to you on that
one
Conor
"Sitaram Chamarty" <sitaramc@gmail.com> wrote in message
news:slrnglf3qh.c7j.sitaramc@sitaramc.homelinux.net...
> 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!)
>
> The git glossary makes no mention of "tip", so this is
> probably "unblessed" :-)
>
next prev parent reply other threads:[~2008-12-29 0:51 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
2008-12-29 0:51 ` Zorba
2008-12-29 0:48 ` Zorba [this message]
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='gj96pl$885$4@ger.gmane.org' \
--to=cr@altmore.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.