clarify, now that we also have immutable directories, which kind of directory we mean here
[Imported from Trac: page Capabilities, version 12]
parent
0d352f613d
commit
9b75ed66e3
|
@ -1,6 +1,6 @@
|
||||||
# Capabilities
|
# 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:
|
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 <anything else>
|
13: unknown/future capability strings <anything else>
|
||||||
|
|
||||||
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
|
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
|
non-directory mutable files aren't used very much. All normal data files are
|
||||||
uploaded into immutable files by default.
|
uploaded into immutable files by default.
|
||||||
|
|
Loading…
Reference in a new issue