From: "Shawn O. Pearce" <spearce@spearce.org>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: repo corruption - Egit's fault?
Date: Fri, 18 Dec 2009 10:16:13 -0800 [thread overview]
Message-ID: <20091218181613.GA10687@spearce.org> (raw)
In-Reply-To: <76c5b8580912181006p2aef9d2fj95bb4c8456d965b@mail.gmail.com>
Eugene Sajine <euguess@gmail.com> wrote:
> When I???m looking at the bare repo in CGit ??it shows me ??Bad object:
> and object SHA-1 instead of ??the tree.
>
> As the only difference between this project and about 30 others was
> that there was an additional branch pushed via Egit I suspect that
> this is what screwed up things, but I ???m not sure??? I???m in progress of
> testing it I don???t know if I will be able to reproduce.
Its a somewhat known problem, but thus far has only shown up in
contexts where I'm unable to get enough data to debug the problem.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=286653
> Please, advise if this can be fixed and which options I have if it
> will happen again (how to properly and quickly restore bare repo)
Delete the branch and repush it. The bug is that EGit didn't push
all of the objects needed by the branch. If you put the missing
objects from the source client into the server repository, it'll
be fine.
To prevent this in the future, you can force a server to check during
push by enabling receive.fsckObjects in the server repository's
configuration file. A broken EGit client will have the push
rejected immediately.
--
Shawn.
next prev parent reply other threads:[~2009-12-18 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 18:06 repo corruption - Egit's fault? Eugene Sajine
2009-12-18 18:16 ` Shawn O. Pearce [this message]
2009-12-18 18:30 ` Eugene Sajine
2009-12-18 18:51 ` Eugene Sajine
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=20091218181613.GA10687@spearce.org \
--to=spearce@spearce.org \
--cc=euguess@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