Changes between Version 52 and Version 53 of SftpFrontend

Timestamp:

2010-10-24T17:43:31Z (14 years ago)

Author:

davidsarah

Comment:

more .txt -> .rst

SftpFrontend

@@ -21 +21 @@
 Since Tahoe uses capability access control rather than Unix-style permissions, the permission bits seen by SFTP clients are only an approximation chosen to avoid confusing client programs. In particular the 'user', 'group' and 'world' permissions on a Tahoe file will always be the same. It is possible to clear all of the 'w' bits on a file, which will prevent that file from being opened for writing, but note that its directory entry can still be replaced via a write cap to the directory.
 
-See the last section of [source:docs/frontends/FTP-and-SFTP.txt FTP-and-SFTP.txt] for information on how the SFTP frontend treats immutable and mutable files.
+See the last section of [source:docs/frontends/FTP-and-SFTP.rst FTP-and-SFTP.rst] for information on how the SFTP frontend treats immutable and mutable files.
 
-The '{{{ctime}}}' and '{{{mtime}}}' attributes will always be the same, and are set from the Tahoe {{{linkmotime}}} timestamp, which is changed only when the link from the parent directory is modified (see the 'About the metadata' section of [source:doc/frontends/webapi.txt webapi.txt]). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.
+The '{{{ctime}}}' and '{{{mtime}}}' attributes will always be the same, and are set from the Tahoe {{{linkmotime}}} timestamp, which is changed only when the link from the parent directory is modified (see the 'About the metadata' section of [source:doc/frontends/webapi.rst webapi.rst]). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.