From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Subject: error: git checkout-index: unable to write file
Date: Thu, 4 Nov 2010 14:00:07 -0500 [thread overview]
Message-ID: <20101104190007.GA17101@burratino> (raw)
Hi gitsters,
Just tried cloning an enormous repo to /tmp (which uses tmpfs)
and got
error: git checkout-index: unable to write file webkit/tools/test_shell/resources/textAreaResizeCorner.png
error: git checkout-index: unable to write file webkit/tools/test_shell/run_all_tests.cc
error: git checkout-index: unable to write file webkit/tools/test_shell/simple_appcache_system.cc
error: git checkout-index: unable to write file webkit/tools/test_shell/simple_appcache_system.h
[etc].
Maybe we can do better? It seems non-ideal in a few ways:
1) it is not checkout-index but read-tree -m that prints the message
2) errno is forgotten
3) I would prefer if "git clone" errored out quickly for ENOSPC instead
of continuing to fill in the cracks with what small files it can
find. Though I suppose the current behavior is better for errors
like EPERM and ENAMETOOLONG, so I can't complain much.
next reply other threads:[~2010-11-04 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 19:00 Jonathan Nieder [this message]
2010-11-04 19:22 ` error: git checkout-index: unable to write file Jeff King
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=20101104190007.GA17101@burratino \
--to=jrnieder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.