[lkml]   [2011]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates

* <> wrote:

> On Tue, 11 Oct 2011 07:50:17 +0200, Ingo Molnar said:
> > $ git pull 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.



 \ /
  Last update: 2011-10-12 10:11    [W:0.055 / U:6.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site