From: Sam Ravnborg <sam@ravnborg.org>
To: git@vger.kernel.org
Subject: git cole give unexpected error message
Date: Tue, 13 Dec 2005 22:28:20 +0100 [thread overview]
Message-ID: <20051213212820.GB5232@mars.ravnborg.org> (raw)
Encountered following minor issue today:
Executed:
sam@mars ~/work $ git clone git://git.kernel.org/pub/scm/lib/klibc/klibc.git viggo
defaulting to local storage area
fatal: unexpected EOF
The errormessage "fatal: unexpected EOF" did not immediately tell me
that the requested git repository did not exists.
But I corrected the path and tried again:
sam@mars ~/work $ git clone git://git.kernel.org/pub/scm/libs/klibc/klibc.git viggo
viggo already exists.
So one can see that git did not clean up after the faulty clone.
It would be nice if git:
1) Displayed a more meaningfull error message
2) Cleaned up so I did not have to do a manual rm -rf viggo
cogito being a nice porcelain gives the git errormessage but manage to
clean up when the clone fails.
So also cogito would benefit from a more descriptive errormessage.
Sam
next reply other threads:[~2005-12-13 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 21:28 Sam Ravnborg [this message]
2005-12-13 22:28 ` git cole give unexpected error message Petr Baudis
2005-12-14 9:36 ` Andreas Ericsson
2005-12-14 11:41 ` Petr Baudis
2005-12-14 21:20 ` Sam Ravnborg
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=20051213212820.GB5232@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).