Possible excessive HEAD branch for gdb.git

[Jan Kratochvil <jan dot kratochvil at redhat dot com>]

Hi Jim,

I had some problems with:

$ git clone git://sourceware.org/git/archer.git
[...]
$ git pull origin
>From ssh://sourceware.org/git/archer
 + d77cced...e2fb0c1 HEAD       -> origin/HEAD  (forced update)
Already up-to-date.
$ git checkout master
Already on 'master'
Your branch is ahead of 'origin/master' by 115 commits.
$ git pull origin
>From ssh://sourceware.org/git/archer
   e2fb0c1..d77cced  master     -> origin/master
Already up-to-date.
$ git checkout master
Already on 'master'

found out it got fixed by:

$ git push origin :HEAD
To ssh://sourceware.org/git/archer.git
 - [deleted]         HEAD

HEAD has no meaning to be present on the server and as one can see in some
cases it may cause some problems.

As current archer.git/gdb.git came from local clones/checkouts HEAD was present
there.

Deleted HEAD now from `archer.git'.  Suggesting one should delete it also from
gdb.git but:

* I see no actual problems HEAD existence would cause for `gdb.git'.

* I even tried to do it but it failed for: ssh://sourceware.org/git/gdb.git
  error: unable to push to unqualified destination: HEAD
  The destination refspec neither matches an existing ref on the remote nor
  begins with refs/, and we are unable to guess a prefix based on the source ref.
  fatal: The remote end hung up unexpectedly
  error: failed to push some refs to 'ssh://sourceware.org/git/gdb.git'

Sorry I did not delete it in advance.


Thanks,
Jan