Re: Errors when updating an old git.git repository
- From
- Hannu Koivisto <azure@iki.fi>
- Date
- Dec 27, 2006, 00:45 UTC
- Message-ID
- <877iwew4iw.fsf@trews52.bothi.fi>
- In-Reply-To
- <Pine.LNX.4.63.0612262350070.19693@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 26 Dec 2006, Hannu Koivisto wrote: > > Git works quite as expected here, so there is nothing to fix.
Since the documentation didn't seem to specify what happens when a remote branch is deleted (I'm assuming that's the case), _I_ didn't expect it.
Show 10 quoted lines
>> error: no such remote ref refs/heads/jc/bind >> error: no such remote ref refs/heads/jc/bind-2 >> error: no such remote ref refs/heads/gb/diffdelta > > Since you said it is an older git repository, I guess that in your > .git/remotes/origin are some lines like this: > > Pull: refs/heads/jc/bind:refs/heads/jc/bind > > 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.
-- Hannu