From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 01 Sep 2011 03:18:40 GMT
Subject: Re: [PATCH 1/2] remote: write correct fetch spec when renaming remote 'remote'
Message-ID: <7vk49tx84v.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20110901024211.GC31838@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> Actually, I think it's better to be more conservative, and rename only:
>
>   refs/remotes/$OLD/
>
> into
>
>   refs/remotes/$NEW/

Thanks.

I wholeheartedly agree with this. It would let me sleep better if we did
this rewriting only when remote.$name.fetch is set exactly to its default
value, "+refs/heads/*:refs/origin/$name/*" (it is Ok if the leading '+' is
missing, though), and we didn't touch either config nor the existing
tracking refs at all otherwise, and gave warning saying we didn't do
anything to them.