summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-11-20 19:16:23 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-11-20 19:16:23 -0400
commit1c584fc0707347c3a4b2a467b191ecec8dc030f0 (patch)
tree78fe5f72d462ce2d374107d64d105b8f6904bd1e /doc
parent06de511c8033c92ad5ec01bbbd6c284a991bcfd4 (diff)
devblog
Diffstat (limited to 'doc')
-rw-r--r--doc/devblog/day_61__damage_driven_development__II.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/devblog/day_61__damage_driven_development__II.mdwn b/doc/devblog/day_61__damage_driven_development__II.mdwn
new file mode 100644
index 000000000..605a3878d
--- /dev/null
+++ b/doc/devblog/day_61__damage_driven_development__II.mdwn
@@ -0,0 +1,15 @@
+Pushed out a minor release of git-annex today, mostly to fix build problems
+on Debian. No strong reason to upgrade to it otherwise.
+
+Continued where I left off with the Git.Destroyer. Fixed quite a lot of
+edge cases where git repair failed due to things like a corrupted .git/HEAD
+file (this makes git think it's not in a git repository), corrupt
+git objects that have an unknown object type and so crash git hard, and
+an interesting failure mode where git fsck wants to allocate 116 GB of
+memory due to a corrupted object size header. Reported that last to the git
+list, as well as working around it.
+
+At the end of the day, I ran a test creating 10000 corrupt git
+repositories, and **all** of them were recovered! Any improvements will
+probably involve finding new ways to corrupt git repositories that my code
+can't think of. ;)