From: Stefan Beller <sbeller@google.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Michael J Gruber <git@drmicha.warpmail.net>
Cc: Jacob Keller <jacob.keller@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [BUG?] HEAD detached at HEAD
Date: Fri, 18 Sep 2015 10:32:09 -0700 [thread overview]
Message-ID: <CAGZ79kZxAwMvv6UoZLBd2wTOdj1DFWKQqSPBYL449KSokA8DQQ@mail.gmail.com> (raw)
In-Reply-To: <vpqeghviqu1.fsf@anie.imag.fr>
On Fri, Sep 18, 2015 at 10:23 AM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Jacob Keller <jacob.keller@gmail.com> writes:
>
>> On Fri, Sep 18, 2015 at 9:59 AM, Matthieu Moy
>> <Matthieu.Moy@grenoble-inp.fr> wrote:
>>> I'm getting it even if there's a tag and/or a branch pointing to the
>>> same commit.
>>>
>>> Any idea what's going on?
>>
>> Any chance you accidentally made a branch or tag named HEAD?
>
> Nice try ;-), but no:
I was playing around with origin/master and origin/pu and
I cannot reproduce this bug.
However maybe Michael as the author of 4b063186
(2015-03-03 branch: name detached HEAD analogous to status)
can help here ?
>
> $ git status
> HEAD detached at HEAD
> nothing to commit, working directory clean
>
> $ git for-each-ref
> 16aa1796fb487fc7178ceef0525fed80284a4c52 commit refs/heads/master
> 16aa1796fb487fc7178ceef0525fed80284a4c52 commit refs/tags/foo
>
> $ git rev-parse HEAD
> 16aa1796fb487fc7178ceef0525fed80284a4c52
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-09-18 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 16:59 [BUG?] HEAD detached at HEAD Matthieu Moy
2015-09-18 17:08 ` Jacob Keller
2015-09-18 17:23 ` Matthieu Moy
2015-09-18 17:32 ` Stefan Beller [this message]
2015-09-18 19:09 ` Matthieu Moy
2015-09-21 7:31 ` Michael J Gruber
2015-09-21 7:39 ` Michael J Gruber
2015-09-21 7:42 ` Matthieu Moy
2015-09-21 17:20 ` Junio C Hamano
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=CAGZ79kZxAwMvv6UoZLBd2wTOdj1DFWKQqSPBYL449KSokA8DQQ@mail.gmail.com \
--to=sbeller@google.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
/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).