From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-35900-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 11443 invoked by alias); 9 Oct 2009 08:55:38 -0000
Received: (qmail 11435 invoked by uid 22791); 9 Oct 2009 08:55:37 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 09 Oct 2009 08:55:33 +0000
Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) 	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n998tUu4008392; 	Fri, 9 Oct 2009 04:55:30 -0400
Received: from hase.home (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) 	by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n998tSBk012341; 	Fri, 9 Oct 2009 04:55:29 -0400
From: Andreas Schwab <schwab@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Jim Meyering <jim@meyering.net>, gdb@sourceware.org
Subject: Re: Possible excessive HEAD branch for gdb.git
References: <20091008211555.GA5939@host0.dyn.jankratochvil.net>
X-Yow: I'm in DISGUISE as a BAGGAGE CHECKER....I can watch the house, if it's  ORANGE...
Date: Fri, 09 Oct 2009 08:55:00 -0000
In-Reply-To: <20091008211555.GA5939@host0.dyn.jankratochvil.net> (Jan 	Kratochvil's message of "Thu, 8 Oct 2009 23:15:56 +0200")
Message-ID: <m37hv5osjj.fsf@hase.home>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-10/txt/msg00173.txt.bz2

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