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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111012080711.GM18618@elte.hu>
Date:	Wed, 12 Oct 2011 10:07:14 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Valdis.Kletnieks@...edu, git@...r.kernel.org
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates


* Valdis.Kletnieks@...edu <Valdis.Kletnieks@...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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/