From: Bernie Innocenti <bernie@codewiz.org>
To: git@vger.kernel.org
Cc: Giovanni Bajo <rasky@develer.com>
Subject: Obfuscated error message
Date: Wed, 11 Mar 2009 05:24:58 +0100 [thread overview]
Message-ID: <49B73D1A.4050605@codewiz.org> (raw)
A friend who uses Mercurial pointed this out as a reson why
Git is evil:
rasky@lilax:~/src$ git clone git://www.develer.com/doesnt-exist
Initialized empty Git repository in /home/rasky/src/doesnt-exist/.git/
fatal: The remote end hung up unexpectedly
Plus, the directory was not really there :-)
rasky@lilax:~/src$ hg clone hg://www.develer.com/doesnt-exist
abort: repository hg://www.develer.com/doesnt-exist not found!
rasky@lilax:~/src$ svn co svn://www.develer.com/doesnt-exist
svn: URL 'svn://www.develer.com/doesnt-exist' doesn't exist
--
// Bernie Innocenti - http://www.codewiz.org/
\X/ Sugar Labs - http://www.sugarlabs.org/
next reply other threads:[~2009-03-11 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 4:24 Bernie Innocenti [this message]
2009-03-11 4:28 ` Obfuscated error message Bernie Innocenti
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=49B73D1A.4050605@codewiz.org \
--to=bernie@codewiz.org \
--cc=git@vger.kernel.org \
--cc=rasky@develer.com \
/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).