From: Jeff King <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] howto: document more tools for recovery corruption Date: Wed, 1 Apr 2015 20:49:55 -0400 [thread overview] Message-ID: <20150402004955.GA25634@peff.net> (raw) In-Reply-To: <email@example.com> On Wed, Apr 01, 2015 at 03:21:16PM -0700, Junio C Hamano wrote: > Jeff King <firstname.lastname@example.org> writes: > > > Long ago, I documented a corruption recovery I did and gave > > some C code that I used to help find a flipped bit. I had > > to fix a similar case recently, and I ended up writing a few > > more tools. I hope nobody ever has to use these, but it > > does not hurt to share them, just in case. > > I am having a hard time deciding if I should take the Date: header > of the patch e-mail into consideration. The munge thing looks > serious enough, though. Heh, no, this is sadly a serious thing that I did today (but I was able to detect and correct a single flipped bit in a 60MB packfile, which is kind of neat, I guess). I hesitated sending them at all because they are not really note-worthy. OTOH, during today's exercise I found the instructions and sample program I had written last time to be very useful, so perhaps it can help somebody (or even me) at some later today. -Peff
prev parent reply other threads:[~2015-04-02 0:50 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 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 [this message]
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20150402004955.GA25634@peff.net \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] howto: document more tools for recovery corruption' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).