aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--README6
1 files changed, 3 insertions, 3 deletions
diff --git a/README b/README
index aca9234..ab70713 100644
--- a/README
+++ b/README
@@ -15,7 +15,7 @@ TODO:
+ Make inflate/deflate block based as needed, so we don't have to do a
bunch of work up front and waste a bunch of space on disk
- done
-- Make files just contain a backing storage key, this key will reference
++ Make files just contain a backing storage key, this key will reference
what we have in it now (the data list and stat info) so that complete
duplicate files will not take up a few extra megs and still be able to
have their own permissions and stuff
@@ -26,7 +26,7 @@ TODO:
- fsck:
- test each chunk < last is a full block size (this would be a good
assert too)
-- delete unused chunks (refcounting)
++ delete unused chunks (refcounting)
- pack multiple chunks in to "super chunks" like cromfs/squashfs to get better
compression (e.g. 4M of data will compress better than that same file
split in to 4 1M pieces and compressed individually presumably)
@@ -39,7 +39,7 @@ TODO:
be swapped out since they are generic
- Maybe compression method doesn't belong in Chunk? it should be part of
storage (for super-chunks?) or should super-chunks be a "standard" part
-- Add refcounting so we can expire chunks, or would a reverse list be
++ Add refcounting so we can expire chunks, or would a reverse list be
better?
- If we separate metadata from chunks then we can just rebuild the
metadata for fsck