From: Ingo Molnar <mingo@elte.hu>
To: Valdis.Kletnieks@vt.edu, git@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates
Date: Wed, 12 Oct 2011 10:07:14 +0200 [thread overview]
Message-ID: <20111012080711.GM18618@elte.hu> (raw)
In-Reply-To: <20002.1318367320@turing-police.cc.vt.edu>
* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> 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
next parent reply other threads:[~2011-10-12 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111010133852.829771373@goodmis.org>
[not found] ` <20111011055017.GA32616@elte.hu>
[not found] ` <20002.1318367320@turing-police.cc.vt.edu>
2011-10-12 8:07 ` Ingo Molnar [this message]
2011-10-12 14:19 ` [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates Jeff King
2011-10-12 16:29 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111012080711.GM18618@elte.hu \
--to=mingo@elte.hu \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).