Subject: Re: git-fetch question/bug

From: Jakub Narebski <[email-masked]>
Date: Fri, 14 Mar 2008 08:52:58 +0100

Junio C Hamano wrote:

> "Govind Salinas" <[email-masked]> writes:
> 
>> ... git-fetch when I discovered that it does not return
>> error when the
>> fetch fails due to it not being a ff...
> 
> I think this is a regression introduced when "git-fetch" was
> re-implemented in C.  git-fetch--tool's native-store subcommand seems to
> have signaled this as an error, and it is reasonable to expect an error
> exit from the command in this case.
> 
> Probably something like this?

[...]

Wouldn't it be better to distinguish somehow remote side errors (like for
example: could not connect to remote server) and local side errors (like
fetch refused because of being not fast-forward)? The former are usually
not recoverable (unless it is URL that is mistyped), the latter could be
usually resolved (forced for example)...

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git