summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-03-12 16:31:41 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-03-12 16:31:41 -0400
commit8540183a02345843a7869521cd65abbe658b4e51 (patch)
treeb85fb2aa268b5d044692e48742d61852c9faef16
parent25809ce2e0861a54ec63a414037b95fe29acc6df (diff)
close
-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..d02638d0e 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.
+> [[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
currently present in the repository (possibly using a bloom filter again),