From 9b75ed66e3483b6f4d1f3a7e2cf3e82e7de69fcc Mon Sep 17 00:00:00 2001 From: zooko <> Date: Wed, 1 Jun 2011 22:32:05 +0000 Subject: [PATCH] clarify, now that we also have immutable directories, which kind of directory we mean here [Imported from Trac: page Capabilities, version 12] --- Capabilities.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Capabilities.md b/Capabilities.md index e9ad5e3..8523fb4 100644 --- a/Capabilities.md +++ b/Capabilities.md @@ -1,6 +1,6 @@ # Capabilities -An overview from the mailing list archives - originally by [Feb 2009 - Brian Warner](http://allmydata.org/pipermail/tahoe-dev/2009-February/001110.html), +An overview from the mailing list archives - originally by [Feb 2009 - Brian Warner](http://tahoe-lafs.org/pipermail/tahoe-dev/2009-February/001110.html), but updated to take into account literal caps and immutable directories: ``` @@ -22,7 +22,7 @@ but updated to take into account literal caps and immutable directories: 13: unknown/future capability strings -In Tahoe-LAFS, directories are built out of mutable files (a directory is really +In Tahoe-LAFS, mutable directories are built out of mutable files (a mutable directory is really just a particular way to interpret the contents of a given mutable file), and non-directory mutable files aren't used very much. All normal data files are uploaded into immutable files by default.