From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Martin Fick <mfick@codeaurora.org>, git@vger.kernel.org
Subject: Re: pack corruption post-mortem
Date: Thu, 17 Oct 2013 08:47:05 -0700 [thread overview]
Message-ID: <xmqqfvrz3nnq.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20131017003546.GA12439@sigill.intra.peff.net> (Jeff King's message of "Wed, 16 Oct 2013 20:35:47 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Oct 16, 2013 at 09:41:16AM -0600, Martin Fick wrote:
>
>> I have nightmares about this sort of thing every now and
>> then, and we even experience some corruption here and there
>> that needs to be fixed (mainly missing objects when we toy
>> with different git repack arguments). I cannot help but
>> wonder, how we can improve git further to either help
>> diagnose or even fix some of these problems? More inline
>> below...
>
> In general, I don't think we know enough about patterns of recovery
> corruption to say which commands would definitely be worth implementing.
> Part of the reason I wrote this up is to document this one case. But
> this is the first time in 7 years of git usage that I've had to do this.
> So I'd feel a little bit better about sinking time into it after seeing
> a few more cases and realizing where the patterns are.
There was one area in our Documentation/ set we used to use to keep
this kind of message almost as-is; perhaps this message fits there?
next prev parent reply other threads:[~2013-10-17 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 8:34 pack corruption post-mortem Jeff King
2013-10-16 8:59 ` Duy Nguyen
2013-10-16 15:41 ` Martin Fick
2013-10-17 0:35 ` Jeff King
2013-10-17 15:47 ` Junio C Hamano [this message]
2013-10-25 7:55 ` Jeff King
2013-10-17 1:06 ` Duy Nguyen
2013-10-19 10:32 ` Duy Nguyen
2013-10-19 14:41 ` Nicolas Pitre
2013-10-19 19:17 ` Shawn Pearce
2013-10-20 20:56 ` Nicolas Pitre
2013-10-20 4:44 ` Duy Nguyen
2013-10-20 21:08 ` Nicolas Pitre
2015-04-01 21:08 ` [PATCH] howto: document more tools for recovery corruption Jeff King
2015-04-01 22:21 ` Junio C Hamano
2015-04-02 0:49 ` Jeff King
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=xmqqfvrz3nnq.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mfick@codeaurora.org \
--cc=peff@peff.net \
/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.