Re: RFC Failover url for fetches?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 24, 2016, 16:54 UTC
- Message-ID
- <xmqq1sz58z74.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <7fdaa160-9262-5d52-7035-8362ca94beea@gmail.com>
Jakub Narębski <jnareb@gmail.com> writes:
Show 14 quoted lines
>> As to fetching from two or more places as "fallback", I am >> moderately negative to add it as a dumb feature that does nothing >> more than "My fetch from A failed, so let's blindly try it from B". >> I'd prefer to keep the "My fetch from A is failing" knowledge near >> the surface of end user's consciousness as a mechanism to pressure A >> to fix it--that way everybody who is fetching from A benefits. >> After all, doing "git remote add B" once (you'd need to tell the URL >> for B anyway to Git) and issuing "git fetch B" after seeing your >> regular "git fetch" fails once in a blue moon is not all that >> cumbersome, I would think. > > One would need to configure fallback B remote to use the same > remote-branch namespace as remote A, if it is to be used as fallback, > I would think.
Yeah, I left it out because I thought that was obvious, but spelling it out explicitly may have helped those who weren't reading carefully.
Thanks