From: "Denis Bueno" <dbueno@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Recovering from repository corruption
Date: Tue, 10 Jun 2008 16:28:43 -0400 [thread overview]
Message-ID: <6dbd4d000806101328k1fc913f2ia55c3e44273ec5ad@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806101317100.3101@woody.linux-foundation.org>
On Tue, Jun 10, 2008 at 16:23, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Tue, 10 Jun 2008, Denis Bueno wrote:
>>
>> You're onto something:
>>
>> [dorothy.local /tmp <Tue Jun 10> <16:02:08>]
>> tmp[176] > git clone file:///Volumes/work/identity.fb/
>
> [ successful ]
>
> Hmm. Scary. That should *not* have been successful with a corrupt repo.
>
> Unless you have done a .grafts file to hide the corruption, or something
> like that?
I intended to do that, yes, and I think I was successful. (I only say
I "intended to" --- instead of "I did" --- because I read the
documentation for the grafts file elsewhere on this list, and not in
some more "blessed" location.)
> Have you saved away the original corrupt repo (the whole .git directory as
> a tar-ball, for example)? And is the data public and non-embarrassing
> enough so that you could make it available for some post-corruption
> analysis? Even if we cannot help recover it, real-life corruption is
> always interesting to see if only as a test-case to make sure that git
> notices it as quickly as possible.
I do have bunches of personal information in the repo, unfortunately.
The particular *file* involved in the corruption, however, is fine for
all to view. Is that useful?
--
Denis
next prev parent reply other threads:[~2008-06-10 20:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:26 Recovering from repository corruption Denis Bueno
2008-06-10 17:55 ` Jakub Narebski
2008-06-10 19:38 ` Denis Bueno
2008-06-10 19:59 ` Jakub Narebski
2008-06-10 20:03 ` Denis Bueno
2008-06-10 20:14 ` Jakub Narebski
2008-06-10 20:35 ` Denis Bueno
2008-06-10 20:23 ` Linus Torvalds
2008-06-10 20:28 ` Denis Bueno [this message]
2008-06-10 21:09 ` Linus Torvalds
2008-06-10 21:22 ` Denis Bueno
2008-06-10 21:48 ` Linus Torvalds
2008-06-10 22:09 ` Denis Bueno
2008-06-10 22:25 ` Tarmigan
2008-06-10 22:41 ` Denis Bueno
2008-06-10 22:45 ` Linus Torvalds
2008-06-10 23:00 ` Linus Torvalds
2008-06-11 0:43 ` Nicolas Pitre
2008-06-11 1:39 ` Linus Torvalds
2008-06-11 1:47 ` Nicolas Pitre
2008-06-10 21:27 ` Denis Bueno
2008-06-10 22:52 ` Junio C Hamano
2008-06-11 23:21 ` To graft or not to graft... (Re: Recovering from repository corruption) Stephen R. van den Berg
2008-06-11 23:34 ` Jakub Narebski
2008-06-11 23:39 ` Linus Torvalds
2008-06-12 7:14 ` Johan Herland
2008-06-12 7:47 ` Jeff King
2008-06-12 10:21 ` Johan Herland
2008-06-12 12:20 ` Stephen R. van den Berg
2008-06-10 19:40 ` Recovering from repository corruption Nicolas Pitre
2008-06-10 19:42 ` Denis Bueno
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=6dbd4d000806101328k1fc913f2ia55c3e44273ec5ad@mail.gmail.com \
--to=dbueno@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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).