From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [HELP] Corrupted repository
Date: Sat, 22 Jun 2013 00:45:47 +0530 [thread overview]
Message-ID: <CALkWK0kLmdbooWUw-x+TBk-fB_XDFQzyu6Q8yb1Prsgi3FD67A@mail.gmail.com> (raw)
In-Reply-To: <7vzjujl267.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> A tl;dr is that we _trust_ our refs and everything reachable from
> them has to be complete. If that is not the case, things will not
> work, and it is not a priority to add workarounds in the normal
> codepath to slow things down.
Makes sense.
> That does not forbid an addition of "git recover-corrupted-repo"
> command, whose "assume everything might be broken" code is not
> shared with the fastpath of other commands.
I'm not looking for a kitchen-sink command: I'm looking for a
well-documented toolset to precisely fix corruptions. We have some
corruption tests in our testsuite already: I think I'll start digging
there.
Thanks.
next prev parent reply other threads:[~2013-06-21 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 10:49 [HELP] Corrupted repository Ramkumar Ramachandra
2013-06-21 16:22 ` Junio C Hamano
2013-06-21 16:44 ` Ramkumar Ramachandra
2013-06-21 19:00 ` Junio C Hamano
2013-06-21 19:15 ` Ramkumar Ramachandra [this message]
2013-06-23 17:48 ` Matthieu Moy
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=CALkWK0kLmdbooWUw-x+TBk-fB_XDFQzyu6Q8yb1Prsgi3FD67A@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).