Re: Sometimes "Failed to find remote refs" means "try git-fetch --no-tags"
- From
Horst H. von Brand <vonbrand@inf.utfsm.cl>
- Date
- Nov 15, 2006, 21:13 UTC
- Message-ID
- <200611152113.kAFLDgZO005651@laptop13.inf.utfsm.cl>
- In-Reply-To
- <junkio@cox.net>
Junio C Hamano <junkio@cox.net> wrote:
[...]
> However "fetch --no-tags" from http upstream is a band-aid to > hide that the upstream repository has stale info/refs, and I do > not think we would want to encourage the band-aid. Rather, the > message should say "yell loudly at the repository owner" ;-).
I'm seeing this gem here:
[vonbrand@laptop13 git]$ git pull fatal: read error (Connection reset by peer) Fetch failure: git://git.kernel.org/pub/scm/git/git.git fatal: read error (Connection reset by peer) Failed to find remote refs No changes.
Who shall I yell at? ;-)
Seriously, this is broken. I get 4 different error messages, plus a (reassuring?) "No changes". Yes, I know this is what I'll see if the machine is overloaded.
-- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239