summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-03-12 16:32:54 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-03-12 16:32:54 -0400
commit6a95240dff4799669ebc14e610f2555c32a86ef3 (patch)
treed21542ea73f6049a3c44c633ca836140b5989ee5
parent77fb50e01a8c66f87fdd79c9c4235074a0f55fa7 (diff)
note fixed
-rw-r--r--doc/todo/git-annex_unused_eats_memory.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/git-annex_unused_eats_memory.mdwn b/doc/todo/git-annex_unused_eats_memory.mdwn
index 91f9a33f7..caaecfa8c 100644
--- a/doc/todo/git-annex_unused_eats_memory.mdwn
+++ b/doc/todo/git-annex_unused_eats_memory.mdwn
@@ -21,6 +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.
+> Fixed in `bloom` branch in git. --[[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
currently present in the repository (possibly using a bloom filter again),