From: "Zorba" <cr@altmore.co.uk>
To: git@vger.kernel.org
Subject: Re: user manual question
Date: Mon, 29 Dec 2008 16:38:30 -0000 [thread overview]
Message-ID: <gjauel$94s$4@ger.gmane.org> (raw)
In-Reply-To: slrnglg90m.olt.sitaramc@sitaramc.homelinux.net
so a detached HEAD is just a HEAD that is not sitting on a tip ?
i.e. if I do $ git reset --hard HEAD^
...pointing HEAD to the previous committ
this is a detached HEAD
(I thought a detached HEAD was maybe a head somewhere on another branch not
"reachable", i.e. a sibling, not a ancestor...
or something like that)
thanks guys
"Sitaram Chamarty" <sitaramc@gmail.com> wrote in message
news:slrnglg90m.olt.sitaramc@sitaramc.homelinux.net...
> On 2008-12-29, Zorba <cr@altmore.co.uk> wrote:
>> Hi Sitaram!
>>
>> Thanks for clearing that one up.
>
> you're welcome; we've all done a bit of struggling I guess!
>
>> 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)
>
> Here's an extract from my notes/internal talks on this:
>
> === basic concepts
> * a branch is "an active line of development"
> * //master//: default branch in a project, by convention
> * //head//: tip of a branch
> * a repo can track many branches, but the working tree is associated
> with
> only one branch at a time
> * //HEAD//: tip of the branch associated with the working tree; this
> is
> where commits go
> ** except when it's "detached"
>
>> Thanks for your other post/reply too - I will be getting back to you on
>> that
>> one
>
> Glad to be of help. I don't consider myself a guru, and am
> constantly waiting for one of the real gurus to strike me
> down with a thunderbolt for saying something stupid :-)
>
next prev parent reply other threads:[~2008-12-29 16:40 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
2008-12-29 1:12 ` Sitaram Chamarty
2008-12-29 6:33 ` Dilip M
2008-12-29 16:38 ` Zorba [this message]
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='gjauel$94s$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 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).