Re: Creating remote branch called HEAD corrupts remote clones

[Felipe Contreras <felipe.contreras@gmail.com>]

On Wed, Apr 27, 2011 at 12:18 PM, Stephen Kelly <steveire@gmail.com> wrote:
> On Tue, Apr 26, 2011 at 8:18 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> On Tue, Apr 26, 2011 at 3:09 PM, Stephen Kelly <steveire@gmail.com> wrote:
>>> Can git have a bug tracker please?
>>
>> So that you would feel comfortable that there would be a bug report
>> gathering dust? Or that it's closed as invalid for lack of
>> information?
>
> If you believe that it is a foregone conclusion that that is the fate
> of all bug trackers, and that that's a reasonable reason for git not
> to have one, then you have had very different experiences to me.
>
> I don't think there's more I can say than that.
>
>>
>>> This is another reminder to fix this bug which is otherwise untrackable.
>>
>> Let's imagine you are posting this to bugzilla: first question?
>> How do you reproduce this?
>
> My initial mail illustrated the problem as best I could:
>
> http://thread.gmane.org/gmane.comp.kde.devel.pim/29534

No problems here:

Initialized empty Git repository in /tmp/remote/
Cloning into alice...
done.
warning: You appear to have cloned an empty repository.
[master (root-commit) 6983153] w
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 file
Counting objects: 3, done.
Writing objects: 100% (3/3), 213 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /tmp/remote/
 * [new branch]      master -> master
[master 116a225] w
 1 files changed, 1 insertions(+), 0 deletions(-)
Counting objects: 5, done.
Writing objects: 100% (3/3), 242 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /tmp/remote/
 * [new branch]      HEAD -> HEAD
Everything up-to-date
Cloning into bob...
done.
From /tmp/remote
   6983153..116a225  HEAD       -> origin/HEAD
Current branch master is up to date.
[master 0951422] w
 1 files changed, 1 insertions(+), 0 deletions(-)
Counting objects: 5, done.
Writing objects: 100% (3/3), 242 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /tmp/remote
   6983153..0951422  HEAD -> master
From /tmp/remote
 + 0951422...116a225 HEAD       -> origin/HEAD  (forced update)
Already up-to-date.
From /tmp/remote
 + 116a225...0951422 master     -> origin/master  (forced update)
Already up-to-date.
From /tmp/remote
 + 0951422...116a225 HEAD       -> origin/HEAD  (forced update)
Already up-to-date.

>> But I already asked you this[1], and you didn't reply. What should one
>> assume but that you don't care enough to help get this fixed.
>>
>> [1] http://article.gmane.org/gmane.comp.version-control.git/165320
>
> Someone else replied. Isn't that enough?

With a different issue that's not really important.

> Other git developers confirmed it's probably an issue. Isn't that enough?
>
> http://thread.gmane.org/gmane.comp.kde.devel.pim/29534/focus=165326

_probably_, many things have happened since then.

Is it still an issue? Doesn't seem so.

-- 
Felipe Contreras