From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git ML <git@vger.kernel.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: gc considered dangerous
Date: Sun, 8 Feb 2009 20:37:53 +0100 [thread overview]
Message-ID: <200902082037.54042.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <BD926B5C-60C2-4A62-9BBC-E31CB26B9BAC@zib.de>
söndag 08 februari 2009 19:24:33 skrev Steffen Prohaska:
> If you have a backup of the corrupted repository right after it got
> corrupted, you can create an index by running "git index-pack" on
> the pack that is lacking an index. This might rescue the lost
> branches.
Yep, but the problem was that git gc was run again on the corrupted repo
so there was only the idx left. (L)Users...
Couldn't we make repack refuse to repack if it discovered left-overs from
a failed repack, or at least make it use the old pack files as reference instead
of ignoring them? Leaving too many objects is, after all, much better than
destroying the repo.
-- robin
next prev parent reply other threads:[~2009-02-08 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 2:47 gc considered dangerous Robin Rosenberg
2009-02-08 14:34 ` Robin Rosenberg
2009-02-08 14:56 ` Johannes Schindelin
2009-02-08 16:04 ` Robin Rosenberg
2009-02-08 17:18 ` Johannes Schindelin
2009-02-08 18:24 ` Steffen Prohaska
2009-02-08 19:37 ` Robin Rosenberg [this message]
2009-02-08 20:00 ` Junio C Hamano
2009-02-08 20:08 ` Robin Rosenberg
2009-02-08 20:10 ` Robin Rosenberg
2009-02-09 6:59 ` Mike Hommey
2009-02-09 7:43 ` Junio C Hamano
2009-02-08 20:09 ` Junio C Hamano
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=200902082037.54042.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
--cc=spearce@spearce.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).