From: Stephen Kelly <steveire@gmail.com>
Date: Wed, 27 Apr 2011 11:37:23 GMT
Subject: Re: Creating remote branch called HEAD corrupts remote clones
Message-ID: <BANLkTikCQkt+e-kA2hbtMh+OFqrrZHt-NQ@mail.gmail.com>
In-Reply-To: <BANLkTi=-d+8ynv5NQ1SZA3V7PMiGiHauCw@mail.gmail.com>

It is not expected.

Alices repo is fubar'd. gitk doesn't work. The info about master being
ahead of remote etc is wrong or git push tells me it worked, though it
doesn't seem to.



stephen@bishop:/tmp/git/alice{master}$ git status
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
# On branch master
# Your branch is ahead of 'origin/master' by 2 commits.
#
nothing to commit (working directory clean)

stephen@bishop:/tmp/git/alice{master}$ git push
Everything up-to-date

stephen@bishop:/tmp/git/alice{master}$ git status
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
# On branch master
# Your branch is ahead of 'origin/master' by 2 commits.
#
nothing to commit (working directory clean)


On Wed, Apr 27, 2011 at 1:32 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Wed, Apr 27, 2011 at 2:29 PM, Stephen Kelly <steveire@gmail.com> wrote:
>> On Wed, Apr 27, 2011 at 11:48 AM, Felipe Contreras
>> <felipe.contreras@gmail.com> wrote:
>>> No problems here:
>>
>> I had another go.
>
> And is that the expected behavior or not? BTW. I used 1.7.5.
>
> --
> Felipe Contreras
>