aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-03-10 17:41:18 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-03-10 17:41:18 -0400
commit53751a4f5f56cd0a0e5a2c2b2dfb48f746ad972a (patch)
tree651c52b6dff4caebbc672d2096b4a90bfaa8b145
parentda32e032f2e5b718fc570d71abaaeac681a383ce (diff)
devblog
-rw-r--r--doc/devblog/day_131__more_bug_squashing.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/devblog/day_131__more_bug_squashing.mdwn b/doc/devblog/day_131__more_bug_squashing.mdwn
new file mode 100644
index 000000000..3c256f1fb
--- /dev/null
+++ b/doc/devblog/day_131__more_bug_squashing.mdwn
@@ -0,0 +1,11 @@
+Squashed three or four more bugs today. Unanswered message backlog is down
+to 27.
+
+The most interesting problem today is that the git-repair code was using
+too much memory when `git-fsck` output a lot of problems (300 thousand!). I
+managed to half the memory use in the worst case (and reduced it much more
+in more likely cases). But, don't really feel I can close that bug yet,
+since really big, really badly broken repositories can still run it out of
+memory. It would be good to find a way to reorganize the code so that the
+broken objects list streams through git-repair and never has to all be
+buffered in memory at once. But this is not easy.