From: Armin Ronacher <armin.ronacher@active-4.com>
To: git@vger.kernel.org
Subject: git clone on out-of-space device causes incorrect errors
Date: Wed, 29 Jan 2014 12:48:30 +0000 [thread overview]
Message-ID: <52E8F89E.6090801@active-4.com> (raw)
Hi,
When cloning onto a device that is out of space to fulfill the whole clone
operation, git will report that the remove repository does not exist:
$ git clone https://github.com/mozilla/flask
Cloning into 'flask'...
remote: Repository not found.
fatal: repository 'https://github.com/mozilla/flask/' not found
This error is misleading. As an example here is what hg does for the same
situation:
$ hg clone https://bitbucket.org/dholth/wheel
destination directory: wheel
requesting all changes
adding changesets
adding manifests
adding file changes
transaction abort!
failed to truncate 00changelog.i
rollback failed - please run hg recover
abort: No space left on device: /Volumes/Disk Image/wheel/.hg/store/.fncache-bt6dzr
Regards,
Armin
reply other threads:[~2014-01-29 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52E8F89E.6090801@active-4.com \
--to=armin.ronacher@active-4.com \
--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).