From: Philip Oakley <philipoakley@talktalk.net>
To: MARIE Alexandre <alexandre.marie@synchrotron-soleil.fr>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [New to the mailing list] Searching for help
Date: Thu, 21 Mar 2019 15:59:51 +0000 [thread overview]
Message-ID: <11e78b8b-77f5-af1c-c362-1ca7aa8585dc@talktalk.net> (raw)
In-Reply-To: <7EF15309FAA2EA4FAB1643CB55D93ED8DBD411@SUN-DAG3.synchrotron-soleil.fr>
Hi Alex
On 21/03/2019 14:11, MARIE Alexandre wrote:
> Hello,
>
> I am searching for help as I made two mistakes, I think.
> First I fetched origin in a 'branch' called temp that is in a 'detached head' state.
> But I can't delete temp by checking out master.
> I don't know how to get rid of this temp detached head.
>
> Second, the detached head causes one issue :
>
> It splits my commits in two, I mean that all the new commits I do are on top of temp detached head but they are not linked.
> I can't get through these two issues with google, I don't know why.
>
> Cheers,
>
> Alex
This list is for the development of Git. There is a googlegroups list
for git users. However..
A detached head simply means that you are looking at a specific commit
((hash number)), rather than the 'latest commit on the branch'.
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.
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.
Philip
next prev parent reply other threads:[~2019-03-21 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:11 [New to the mailing list] Searching for help MARIE Alexandre
2019-03-21 15:59 ` Philip Oakley [this message]
2019-03-21 16:11 ` MARIE Alexandre
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=11e78b8b-77f5-af1c-c362-1ca7aa8585dc@talktalk.net \
--to=philipoakley@talktalk.net \
--cc=alexandre.marie@synchrotron-soleil.fr \
--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.