summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-03-12 16:33:16 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-03-12 16:33:16 -0400
commit59e2feeda146bd37057db42862c4a4efbaf6e95e (patch)
tree31337d8a36de54e0faf57377f5caba4bbee2a3dc /doc/todo
parent94aff8b8786efb1d396fb20fd0d177fce6056a71 (diff)
parent6a95240dff4799669ebc14e610f2555c32a86ef3 (diff)
Merge branch 'master' into bloom
Conflicts: doc/todo/git-annex_unused_eats_memory.mdwn
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/git-annex_unused_eats_memory.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/todo/git-annex_unused_eats_memory.mdwn b/doc/todo/git-annex_unused_eats_memory.mdwn
index d02638d0e..760a6ccf5 100644
--- a/doc/todo/git-annex_unused_eats_memory.mdwn
+++ b/doc/todo/git-annex_unused_eats_memory.mdwn
@@ -21,7 +21,8 @@ in the bloom filter. Since there can be false positives, this might
miss finding some unused keys. The probability/size of filter
could be tunable.
-> [[done]]! --[[Joey]]
+> Fixed in `bloom` branch in git. --[[Joey]]
+>> [[done]]! --[[Joey]]
Another way might be to scan the git log for files that got removed
or changed what key they pointed to. Correlate with keys with content