From d7d0ae3c2c40c9f8294b955c3b8cde37b667aeaa Mon Sep 17 00:00:00 2001 From: david-sarah Date: Sun, 6 Jun 2010 23:16:00 -0700 Subject: [PATCH] FTP-and-SFTP.txt: minor technical correction to doc for 'no-write' flag. --- docs/frontends/FTP-and-SFTP.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/frontends/FTP-and-SFTP.txt b/docs/frontends/FTP-and-SFTP.txt index 281ecfdf..df6c4c0d 100644 --- a/docs/frontends/FTP-and-SFTP.txt +++ b/docs/frontends/FTP-and-SFTP.txt @@ -183,10 +183,10 @@ caps to it will remain valid. (See docs/garbage-collection.txt for how to reclaim the space used by files that are no longer needed.) The 'no-write' metadata field of a directory entry can override this -behaviour. If the 'no-write' field holds a non-empty string (typically -"true"), then a permission error will occur when trying to write to the -file, even if it is in a writeable directory. This does not prevent the -directory entry from being unlinked or replaced. +behaviour. If the 'no-write' field holds a true value, then a permission +error will occur when trying to write to the file, even if it is in a +writeable directory. This does not prevent the directory entry from being +unlinked or replaced. When using sshfs, the 'no-write' field can be set by clearing the 'w' bits in the Unix permissions, for example using the command -- 2.45.2