From: Junio C Hamano <junkio@cox.net>
Date: Wed, 27 Dec 2006 00:58:58 GMT
Subject: Re: Errors when updating an old git.git repository
Message-ID: <7vwt4eb1d9.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <877iwew4iw.fsf@trews52.bothi.fi>

Hannu Koivisto <azure@iki.fi> writes:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> ...
>> So, you _asked_ git to fetch these three branches!
>
> Well, that's true from a technical standpoint, but I didn't add
> those lines to .git/remotes/origin, git did when I cloned the
> repository.  When one updates tracking branches and a branch has
> been deleted in the remote repository, I think it wouldn't be
> insane to expect git also to remove the line (if not the actual
> branch).  If that is not desired, I'd rather the message wasn't an
> error but something along the lines of "note: remote branch jc/bind
> no longer exists, please update .git/remotes/origin".  It's bit odd
> to get errors in a situation that (given the assumption) isn't
> erroneous.

I would be a bit reluctant to remove tracking automagically, but
I fully agree that a comment like that would be needed.

Patches?