From: Junio C Hamano <junkio@cox.net>
To: Hannu Koivisto <azure@iki.fi>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Errors when updating an old git.git repository
Date: Tue, 26 Dec 2006 16:58:58 -0800 [thread overview]
Message-ID: <7vwt4eb1d9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <877iwew4iw.fsf@trews52.bothi.fi> (Hannu Koivisto's message of "Wed, 27 Dec 2006 02:45:11 +0200")
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?
prev parent reply other threads:[~2006-12-27 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 14:49 Errors when updating an old git.git repository Hannu Koivisto
2006-12-26 15:37 ` Lars Hjemli
2006-12-26 19:22 ` Hannu Koivisto
2006-12-26 22:54 ` Johannes Schindelin
2006-12-27 0:22 ` Junio C Hamano
2006-12-27 0:45 ` Hannu Koivisto
2006-12-27 0:58 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vwt4eb1d9.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=azure@iki.fi \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.