-There are two main cases where the behavior of tahoe-1.10.1 differs from that
-of the previous 1.10.0 release:
-
-- "cp DIRCAP/file.txt ./local/missing" , where "./local" is a directory but
- "./local/missing" does not exist. The implication is that you want tahoe to
- create a new file named "./local/missing" and fill it with the contents of
- the tahoe-side DIRCAP/file.txt. In 1.10.0, a plain "cp" would do just this,
- but "cp -r" would do "mkdir ./local/missing" and then create a file named
- "./local/missing/file.txt". In 1.10.1, both "cp" and "cp -r" create a file
- named "./local/missing".
-- "cp -r PARENTCAP/dir ./local/missing", where PARENTCAP/dir/ contains
- "file.txt", and again "./local" is a directory but "./local/missing" does
- not exist. In both 1.10.0 and 1.10.1, this first does "mkdir
- ./local/missing". In 1.10.0, it would then copy the contents of the source
- directory into the new directory, resulting in "./local/missing/file.txt".
- In 1.10.1, following the new rule of "a named directory source refers to
- the directory itself", the tool creates "./local/missing/dir/file.txt".
+There are two main cases where the behavior of Tahoe-LAFS v1.10.1 differs
+from that of the previous v1.10.0 release:
+
+- "``cp DIRCAP/file.txt ./local/missing``" , where "``./local``" is a
+ directory but "``./local/missing``" does not exist. The implication is
+ that you want Tahoe to create a new file named "``./local/missing``" and
+ fill it with the contents of the Tahoe-side ``DIRCAP/file.txt``. In
+ v1.10.0, a plain "``cp``" would do just this, but "``cp -r``" would do
+ "``mkdir ./local/missing``" and then create a file named
+ "``./local/missing/file.txt``". In v1.10.1, both "``cp``" and "``cp -r``"
+ create a file named "``./local/missing``".
+- "``cp -r PARENTCAP/dir ./local/missing``", where ``PARENTCAP/dir/``
+ contains "``file.txt``", and again "``./local``" is a directory but
+ "``./local/missing``" does not exist. In both v1.10.0 and v1.10.1, this
+ first does "``mkdir ./local/missing``". In v1.10.0, it would then copy
+ the contents of the source directory into the new directory, resulting
+ in "``./local/missing/file.txt``". In v1.10.1, following the new rule
+ of "a named directory source refers to the directory itself", the tool
+ creates "``./local/missing/dir/file.txt``".