From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: Florian Breitwieser <florian.bw@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Recover broken git repository?
Date: Tue, 14 Jul 2009 19:52:45 +0200 [thread overview]
Message-ID: <20090714175245.GD9919@scotty.home> (raw)
In-Reply-To: <alpine.LFD.2.01.0907141019380.13838@localhost.localdomain>
Also sprach Linus Torvalds am Tue, 14 Jul 2009 at 10:33:58 -0700:
Hi,
> > $ git commit -m "Some message"
> > error: invalid object 1086b1c606a04bcb78b92d1d411a299d20d18034
> > fatal: Error building trees
I've trapped in a similar problem few days ago on windows using
cygwin.
A simple "git status" told me an invalid object. Just doing
git status corrupted the index file and only this. The reason was a
wrong configured (unseen reconfigured from another script) mount via
cygwin using "textmode" not "binary mode".
After remounting with "binary mode" a simple "git read-tree HEAD"
repaired it. Just the index file had been corrupted.
Stefan
--
Stefan-W. Hahn It is easy to make things.
/ mailto:stefan.hahn@s-hahn.de / It is hard to make things simple.
Please note that according to the German law on data retention,
information on every electronic information exchange with me is
retained for a period of six months.
Bundesgesetzblatt:
http://www.bgblportal.de/BGBL/bgbl1f/bgbl107s3198.pdf
next prev parent reply other threads:[~2009-07-14 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:20 Recover broken git repository? Florian Breitwieser
2009-07-14 14:40 ` Alex Riesen
2009-07-14 14:54 ` Nicolas Sebrecht
2009-07-14 15:20 ` Jakub Narebski
2009-07-14 17:33 ` Linus Torvalds
2009-07-14 17:48 ` Stefan-W. Hahn
2009-07-14 17:52 ` Stefan-W. Hahn [this message]
2009-07-14 18:25 ` [PATCH] Improve on the 'invalid object' error message at commit time Linus Torvalds
2009-07-14 19:43 ` Junio C Hamano
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=20090714175245.GD9919@scotty.home \
--to=stefan.hahn@s-hahn.de \
--cc=florian.bw@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 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).