| commit | 22e07a67f1e0f1374c3f6c530df7ebfd557f8c84 | |
| author | Nicolas Pitre <nico@cam.org> | |
| Mon, 11 Aug 2008 02:55:22 +0000 (10 22:55 -0400) | ||
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Mon, 11 Aug 2008 15:13:10 +0000 (11 16:13 +0100) | ||
| tree | 85bdf0a993eafea9769dec0bd5d0b813035e050f | treesnapshot (tar.gz zip) |
| parent | 0a4d71a207ae231b1e35cf623d6ba36966b1f835 | commitdiff |
How to replace a single corrupt, packed object?
On Fri, 8 Aug 2008, Johannes Schindelin wrote:
> In any case, the pack is too large for me to let my computer repack
> everything, when only one object needs repacking.
By that you mean you cannot/don't want to use repack -f, right?
There _could_ be a way to hack pack-objects so not to reuse bad objects.
However I don't want that to impact the code too much for an
event that hopefully should almost never happens, especially if using -f
does work around it already.
Well, let's see.
[...]
OK, here's what the patch to allow repacking without -f and still using
redundant objects in presence of pack corruption might look like.
Please tell me if that works for you.
On Fri, 8 Aug 2008, Johannes Schindelin wrote:
> In any case, the pack is too large for me to let my computer repack
> everything, when only one object needs repacking.
By that you mean you cannot/don't want to use repack -f, right?
There _could_ be a way to hack pack-objects so not to reuse bad objects.
However I don't want that to impact the code too much for an
event that hopefully should almost never happens, especially if using -f
does work around it already.
Well, let's see.
[...]
OK, here's what the patch to allow repacking without -f and still using
redundant objects in presence of pack corruption might look like.
Please tell me if that works for you.
| builtin-pack-objects.c | diffblobblamehistory |