summaryrefslogtreecommitdiff
path: root/Documentation/howto/recover-corrupted-blob-object.txt
diff options
context:
space:
mode:
authorThomas Ackermann <th.acker66@arcor.de>2012-10-16 17:25:29 (GMT)
committerJunio C Hamano <gitster@pobox.com>2012-10-18 17:51:34 (GMT)
commit1797e5c50c00b514b798f7b0441c86ee71fb0fab (patch)
tree40835d0cb2880348613ba4763ff478a4b246bcca /Documentation/howto/recover-corrupted-blob-object.txt
parent5316c8e9399dacd9e0f7c22132f3ad67186408ed (diff)
downloadgit-1797e5c50c00b514b798f7b0441c86ee71fb0fab.zip
git-1797e5c50c00b514b798f7b0441c86ee71fb0fab.tar.gz
git-1797e5c50c00b514b798f7b0441c86ee71fb0fab.tar.bz2
Documentation/howto: convert plain text files to asciidoc
These were not originally meant for asciidoc, but they are already so close. Mark them up in asciidoc. Signed-off-by: Thomas Ackermann <th.acker@arcor.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/howto/recover-corrupted-blob-object.txt')
-rw-r--r--Documentation/howto/recover-corrupted-blob-object.txt10
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/howto/recover-corrupted-blob-object.txt b/Documentation/howto/recover-corrupted-blob-object.txt
index 323b513..7484735 100644
--- a/Documentation/howto/recover-corrupted-blob-object.txt
+++ b/Documentation/howto/recover-corrupted-blob-object.txt
@@ -3,11 +3,17 @@ From: Linus Torvalds <torvalds@linux-foundation.org>
Subject: corrupt object on git-gc
Abstract: Some tricks to reconstruct blob objects in order to fix
a corrupted repository.
+Content-type: text/asciidoc
+How to recover a corrupted blob object
+======================================
+
+-----------------------------------------------------------
On Fri, 9 Nov 2007, Yossi Leybovich wrote:
>
> Did not help still the repository look for this object?
> Any one know how can I track this object and understand which file is it
+-----------------------------------------------------------
So exactly *because* the SHA1 hash is cryptographically secure, the hash
itself doesn't actually tell you anything, in order to fix a corrupt
@@ -31,19 +37,23 @@ original object, so right now the corrupt object is useless, but it's very
interesting for the future, in the hope that you can re-create a
non-corrupt version.
+-----------------------------------------------------------
So:
> ib]$ mv .git/objects/4b/9458b3786228369c63936db65827de3cc06200 ../
+-----------------------------------------------------------
This is the right thing to do, although it's usually best to save it under
it's full SHA1 name (you just dropped the "4b" from the result ;).
Let's see what that tells us:
+-----------------------------------------------------------
> ib]$ git-fsck --full
> broken link from tree 2d9263c6d23595e7cb2a21e5ebbb53655278dff8
> to blob 4b9458b3786228369c63936db65827de3cc06200
> missing blob 4b9458b3786228369c63936db65827de3cc06200
+-----------------------------------------------------------
Ok, I removed the "dangling commit" messages, because they are just
messages about the fact that you probably have rebased etc, so they're not