Re: [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates

From: Ingo Molnar <mingo@elte.hu>
Date: Oct 12, 2011, 08:07 UTC
Message-ID: <20111012080711.GM18618@elte.hu>
In-Reply-To: <20002.1318367320@turing-police.cc.vt.edu>

* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:

Show 8 quoted lines

> On Tue, 11 Oct 2011 07:50:17 +0200, Ingo Molnar said:
> 
> >  $ git pull git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git tip/perf/core
> >  fatal: The remote end hung up unexpectedly
> 
> Is it possible to get 'git' to say something more informative than 
> "hung up unexpectedly"? "Tree not found, check URL" or similar 
> would be nice...

I've Cc:-ed the Git development list which has lots of very responsive gents on it eager to improve Git.

I see this message dozens of times per year and i am always confused about the message.

Firstly, arguably, typoing something is not 'fatal' really - it's just a resource that was not found on the server.

Secondly, and more importantly, the reason for the failed pull is indeed important to know, if you want to resolve the problem with a minimum fuss:

 - Was it the tree that didnt exist?
 - Or the branch?
 - Or was there some other problem [such as a truly unexpectedly 
                                    closed transport socket]?

It's really useful for a painless UI flow to disambiguate failure messages into clearly actionable variants.

Thanks,

	Ingo