From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Nicolas Pitre <nico@cam.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] make git a bit less cryptic on fetch errors
Date: Mon, 18 Dec 2006 23:22:05 +0000 [thread overview]
Message-ID: <200612182322.15703.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612181505320.18171@xanadu.home>
On Monday 2006, December 18 20:16, Nicolas Pitre wrote:
> - die("unexpected EOF");
> + die("for some reason the remote end hung up unexpectedly");
If we don't know the reason; then saying this makes it sound like we just
couldn't be bothered to write the message. How about just:
"The remote end hung up unexpectedly"
?
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
parent reply other threads:[~2006-12-18 23:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.64.0612181505320.18171@xanadu.home>]
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=200612182322.15703.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
/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