From: "Jeff Whiteside" <jeff.m.whiteside@gmail.com>
To: "Jonas Schneider" <JonasSchneider@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: Broken index file - any hope?
Date: Fri, 3 Oct 2008 15:09:37 -0700 [thread overview]
Message-ID: <3ab397d0810031509i3e54252cp260a78de1d3faf8a@mail.gmail.com> (raw)
In-Reply-To: <48E696CB.6040405@gmx.de>
I don't know if you're new to git, but I used git for about a year
before I knew what the index really was.
Remember, the index file only stores changes you made to the
checkedout code AFTER the last commit, so all your commits are safely
in the tree objects still.
The index is only a place to store changes you made with "git add",
not "git commit".
I'm not sure how you refresh the index file but i would back
everything up and try a "git reset --hard" or something.
On Fri, Oct 3, 2008 at 3:03 PM, Jonas Schneider <JonasSchneider@gmx.de> wrote:
> Shawn O. Pearce schrieb:
>>
>> git read-tree --reset HEAD
>
> Sadly, this doesnt help. I still get the same error.
> But, if I remove the corrupt index file, I get this:
>
> fatal: just how do you expect me to merge 0 trees?
>
> Does not look like a good sign :/
> Are all my branches (branch==tree?) gone? (okay, werent that much)
>
> Thanks anyway :)
> -- Jonas
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-10-03 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 21:51 Broken index file - any hope? Jonas Schneider
2008-10-03 21:53 ` Shawn O. Pearce
2008-10-03 22:03 ` Jonas Schneider
2008-10-03 22:07 ` Shawn O. Pearce
2008-10-03 22:09 ` Jeff Whiteside [this message]
2008-10-04 3:08 ` Linus Torvalds
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=3ab397d0810031509i3e54252cp260a78de1d3faf8a@mail.gmail.com \
--to=jeff.m.whiteside@gmail.com \
--cc=JonasSchneider@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).