From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] index corruption with git commit -p
Date: Sat, 1 Sep 2018 23:41:58 +0200 [thread overview]
Message-ID: <20180901214157.hxlqmbz3fds7hsdl@ltop.local> (raw)
Hi,
I've just had a scary error:
error: index uses $?+? extension, which we do not understand
fatal: index file corrupt
Things were quickly recovered by deleting the index but it clearly
looks to a but to me.
Here are the steps to reproduce it:
$ git clone git://github.com/lucvoo/sparse-dev.git <somedir>
$ cd <somedir>
$ git co index-corruption
$ git rm -r validation/ Documentation/
$ git commit -m <some message> -p
$ git status
error: index uses $?+? extension, which we do not understand
fatal: index file corrupt
The 'extension' pattern '$?+?', can vary a bit, sometimes
it's just '????', but always seems 4 chars.
If the commit command doesn't use the '-p' flag, there is no
problem. The repository itself is not corrupted, it's only
the index. It happends with git 2.18.0 and 2.17.0
-- Luc Van Oostenryck
next reply other threads:[~2018-09-01 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 21:41 Luc Van Oostenryck [this message]
2018-09-01 22:17 ` [BUG] index corruption with git commit -p Ævar Arnfjörð Bjarmason
2018-09-02 5:08 ` Jeff King
2018-09-02 7:12 ` Duy Nguyen
2018-09-02 7:24 ` Jeff King
2018-09-02 7:53 ` Luc Van Oostenryck
2018-09-02 8:02 ` Jeff King
2018-09-04 15:57 ` Junio C Hamano
2018-09-04 16:13 ` Duy Nguyen
2018-09-04 16:38 ` Jeff King
2018-09-04 23:36 ` [PATCH] reopen_tempfile(): truncate opened file Jeff King
2018-09-05 15:27 ` Duy Nguyen
2018-09-05 15:35 ` Jeff King
2018-09-05 15:39 ` Duy Nguyen
2018-09-05 15:48 ` Jeff King
2018-09-05 16:54 ` Junio C Hamano
2018-09-05 16:56 ` Jeff King
2018-09-05 17:01 ` Junio C Hamano
2018-09-05 18:48 ` Luc Van Oostenryck
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180901214157.hxlqmbz3fds7hsdl@ltop.local \
--to=luc.vanoostenryck@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).