RE:[New to the mailing list] Searching for help

From: MARIE Alexandre <alexandre.marie@synchrotron-soleil.fr>
Date: Mar 21, 2019, 16:11 UTC
Message-ID: <7EF15309FAA2EA4FAB1643CB55D93ED8DBD439@SUN-DAG3.synchrotron-soleil.fr>
In-Reply-To: <11e78b8b-77f5-af1c-c362-1ca7aa8585dc@talktalk.net>

Hello Philip

> This list is for the development of Git. There is a googlegroups list
> for git users. However..

Sorry, my mistake, I found this mailing list here[0] where it is written that this is one for asking questions, having comments or reporting bugs.

> A detached head simply means that you are looking at a specific commit
> ((hash number)), rather than the 'latest commit on the branch'.

I think that I kind of understand what is a detached head now, but my problem is when I run: gitk --all I still can see the detached head, whether I am on the 'detached head state' or not.

>  You did not say which OS you were on, or if you prefer the command line,
> or a visual  gui to see the current arrangement of your commits - the
> 'gitk' viewer is useful for the latter.

Sorry about that, I am on Debian.

Show 6 quoted lines

> If you have already made some commits on the 'detached head' then use
> the 'git branch' command, or 'git checkout -b' to create a branch name
> for your new commits (check the manual). Having named the new commits,
> you can get back to link the bits together. You can use 'cherry-pick' to
> pick of individual commits from that new branch onto the new
> destination, or use rebase if there is a series.

The fact is that I fetched a whole rep into a detached head state named temp, but this is not a git branch. So I am stuck trying to delete this whole rep. My history is splitted by two by the rep in detached head state.

Thanks for your response.

Alex

[0] https://git-scm.com/community