This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Possible excessive HEAD branch for gdb.git
- From: Andreas Schwab <schwab at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Jim Meyering <jim at meyering dot net>, gdb at sourceware dot org
- Date: Fri, 09 Oct 2009 10:55:28 +0200
- Subject: Re: Possible excessive HEAD branch for gdb.git
- References: <20091008211555.GA5939@host0.dyn.jankratochvil.net>
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."