Re: user manual question

From: Zorba <cr@altmore.co.uk>
Date: Dec 29, 2008, 17:29 UTC
Message-ID: <gjauel$94s$4@ger.gmane.org>
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...

Show 33 quoted lines

> 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 :-)
>