From: Johannes Sixt <j.sixt@viscovery.net>
To: Yossi Leybovich <sleybo@gmail.com>
Cc: Andreas Ericsson <ae@op5.se>,
git@vger.kernel.org, Yossi Leybovich <sleybo@mellanox.co.il>
Subject: Re: corrupt object on git-gc
Date: Fri, 09 Nov 2007 16:34:38 +0100 [thread overview]
Message-ID: <47347E0E.1040205@viscovery.net> (raw)
In-Reply-To: <4fe79b4b0711090701g7a43cdfdi5e20e5ffb437d7bb@mail.gmail.com>
Yossi Leybovich schrieb:
> [about corrupt loose object '4b9458b3786228369c63936db65827de3cc06200']
You can try to create a clone (after you have fixed up the artificial
breakages that you made). If that goes well, then the bad object is
referenced only from reflogs.
-- Hannes
next prev parent reply other threads:[~2007-11-09 15:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 13:38 corrupt object on git-gc Yossi Leybovich
2007-11-09 13:46 ` Andreas Ericsson
2007-11-09 15:01 ` Yossi Leybovich
2007-11-09 15:34 ` Johannes Sixt [this message]
2007-11-09 15:53 ` Yossi Leybovich
2007-11-09 16:03 ` Johannes Sixt
2007-11-09 16:03 ` Nicolas Pitre
2007-11-09 16:31 ` Yossi Leybovich
2007-11-09 16:52 ` Nicolas Pitre
2007-11-09 16:28 ` Linus Torvalds
2007-11-09 17:28 ` [PATCH] add a howto document about corrupted blob recovery Nicolas Pitre
2007-11-09 17:30 ` Johannes Schindelin
2007-11-26 2:12 ` J. Bruce Fields
2007-11-09 17:53 ` corrupt object on git-gc Yossi Leybovich
2007-11-09 18:02 ` Linus Torvalds
2007-11-09 18:37 ` Yossi Leybovich
2007-11-09 18:55 ` Linus Torvalds
2007-11-09 19:07 ` Mike Hommey
2007-11-09 19:41 ` Yossi Leybovich
2007-11-09 19:52 ` Mike Hommey
[not found] <6C2C79E72C305246B504CBA17B5500C902535D9C@mtlexch01.mtl.com>
[not found] ` <458BC6B0F287034F92FE78908BD01CE814472B3D@mtlexch01.mtl.com>
2007-11-08 23:59 ` Yossi Leybovich
2007-11-09 5:13 ` Christian Couder
2007-11-09 12:16 ` Yossi Leybovich
2007-11-09 17:45 ` Junio C Hamano
2007-11-09 8:10 ` Alex Riesen
2007-11-09 12:23 ` Yossi Leybovich
2007-11-09 12:56 ` Andreas Ericsson
2007-11-09 16:17 ` Nicolas Pitre
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=47347E0E.1040205@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=sleybo@gmail.com \
--cc=sleybo@mellanox.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.