From: Ben Tebulin <nntp.20.jexpert@spamgourmet.com>
To: git@vger.kernel.org
Subject: Re: Git commit error: fatal: Repository has been updated, but unable to write new_index file.
Date: Tue, 27 Mar 2012 13:51:48 +0200 [thread overview]
Message-ID: <jks9k9$c35$1@dough.gmane.org> (raw)
In-Reply-To: <34E530A4-A792-42AC-8C19-5F7CB71FA46C@jetbrains.com>
> fatal: Repository has been updated, but unable to write new_index
> file. Check that disk is not full or quota is not exceeded, and then
> "git reset HEAD" to recover.
>
> Here is the command which IDE executes to make a commit:
>
> # git commit --only -F<message file> -- <several files chosen to
> commit>
I can confirm this issue. I saw this error more than once. And I'm
working with cygwin Git on the command line - but having an IDE (VS in
this case) opened in parallel.
I don't think the issue is about two parallel Git operations in
parallel. I only started one. But more that some file of the working
copy is in access. And Git seems to be much more sensible about those
than i.e. subversion. (No file was "locked")
Sorry - but I cannot tell anything more except that I've experienced
this issue too. Maybe this is a windows specific issue? As a windows
user I had some of them...
next prev parent reply other threads:[~2012-03-27 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 7:35 Git commit error: fatal: Repository has been updated, but unable to write new_index file Kirill Likhodedov
2012-03-27 8:36 ` Kevin
2012-03-27 14:28 ` Kirill Likhodedov
2012-03-27 11:51 ` Ben Tebulin [this message]
2012-03-27 12:20 ` Kevin
2012-05-15 6:34 ` Sylvain
2012-05-15 21:36 ` Heiko Voigt
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 15:17 Kirill Likhodedov
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='jks9k9$c35$1@dough.gmane.org' \
--to=nntp.20.jexpert@spamgourmet.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).