Possible excessive HEAD branch for gdb.git

Possible excessive HEAD branch for gdb.git

[Jan Kratochvil]

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

Re: Possible excessive HEAD branch for gdb.git

[Andreas Schwab]

Jan Kratochvil <jan.kratochvil@redhat.com> writes:

> Hi Jim,
>
> I had some problems with:
>
> $ git clone git://sourceware.org/git/archer.git
              ^^^
> [...]
> $ git pull origin
> From ssh://sourceware.org/git/archer
       ^^^

What did you do in the mean time?

>  + 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.

HEAD is normally pointing to the branch that will be checked out by git
clone by default.  I don't think your problem was related to the
existence of the HEAD symbolic ref.

Andreas.

-- 
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."

Re: Possible excessive HEAD branch for gdb.git

[Jan Kratochvil]

On Fri, 09 Oct 2009 10:55:28 +0200, Andreas Schwab wrote:
> Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> > $ git clone git://sourceware.org/git/archer.git
>               ^^^
> > [...]
> > $ git pull origin
> > From ssh://sourceware.org/git/archer
>        ^^^
> 
> What did you do in the mean time?

There was "ssh" everywhere but I cheated a bit as a new checkout would be too
slow.


> HEAD is normally pointing to the branch that will be checked out by git
> clone by default.

Thanks for the info.  Still after removing HEAD at the parent repository a new
clone checks out "master" for me.


> I don't think your problem was related to the existence of the HEAD symbolic
> ref.

I had a different suspection first that as I did "git repack -A -d" (to save
space) I did see some hashes improperly chosen in ./packed-refs vs.
./info/refs vs. refs/* and I did not know how to easily undo "git repack".
So it may be true the HEAD deletion just could workaround it.

Anyway both master.git and gdb.git look OK at least to me so probably no
change is needed.


Thanks,
Jan

Re: Possible excessive HEAD branch for gdb.git

[Andreas Schwab]

Jan Kratochvil <jan.kratochvil@redhat.com> writes:

> Thanks for the info.  Still after removing HEAD at the parent repository a new
> clone checks out "master" for me.

"master" is the default default :-)

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."