From: Aghiles <aghilesk@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git list <git@vger.kernel.org>
Subject: Re: Useless error message?
Date: Thu, 22 Apr 2010 16:13:53 -0400 [thread overview]
Message-ID: <l2x3abd05a91004221313s2cb89697i3bcbfbcd6ccf6820@mail.gmail.com> (raw)
In-Reply-To: <20100422115625.GJ3563@machine.or.cz>
Hello,
>
> I have seen a lot of users who plainly had a lot of trouble even
> _understanding_ the error message - it is phrased in super-dense
> networking jargon. I think something like
>
> "fatal: Server terminated the connection for unknown reason"
>
> might come a long way (though of course specific error messages would
> still be far more helpful).
>
I would say that:
"fatal: Server terminated the connection."
Is best and actually says what it has to stay. "Unknown reason" sounds like a
godly intervention into the git protocol. Sometimes, the "hung up" message is
given as an extra information that actually causes more harm than good:
% git pull hummus
fatal: 'hummus' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
-- aghiles
prev parent reply other threads:[~2010-04-22 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 21:17 Useless error message? Aghiles
2010-04-21 21:29 ` Kim Ebert
2010-04-21 22:19 ` Jonathan Nieder
2010-04-22 6:33 ` Junio C Hamano
2010-04-22 9:42 ` Jonathan Nieder
2010-04-22 9:59 ` Andreas Ericsson
2010-04-22 10:15 ` Jonathan Nieder
2010-04-22 10:27 ` Andreas Ericsson
2010-04-22 10:38 ` Jonathan Nieder
2010-04-22 12:44 ` Ilari Liusvaara
2010-04-22 22:21 ` [PATCH] daemon: report inaccessible repositories to user Jonathan Nieder
2010-04-22 11:56 ` Useless error message? Petr Baudis
2010-04-22 20:13 ` Aghiles [this message]
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=l2x3abd05a91004221313s2cb89697i3bcbfbcd6ccf6820@mail.gmail.com \
--to=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pasky@suse.cz \
/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).