Support the new --files-from, --no-relative, --no-implied-dirs, and --from0

[rsync/rsync.git] / rsync.yo

diff --git a/rsync.yo b/rsync.yo
index 0b2ec98..bc3b713 100644 (file)
--- a/rsync.yo
+++ b/rsync.yo
@@ -25,7 +25,7 @@ greatly speed up file transfers when the destination file already
 exists.
 
 The rsync remote-update protocol allows rsync to transfer just the
 exists.
 
 The rsync remote-update protocol allows rsync to transfer just the

-differences between two sets of files across the network link, using
+differences between two sets of files across the network connection, using

 an efficient checksum-search algorithm described in the technical
 report that accompanies this package.
 
 an efficient checksum-search algorithm described in the technical
 report that accompanies this package.
 


@@ -251,7 +251,7 @@ files and mail folders, I use a cron job that runs
 
 quote(rsync -Cavz . arvidsjaur:backup)
 
 
 quote(rsync -Cavz . arvidsjaur:backup)
 

-each night over a PPP link to a duplicate directory on my machine
+each night over a PPP connection to a duplicate directory on my machine

 "arvidsjaur".
 
 To synchronize my samba source trees I use the following Makefile
 "arvidsjaur".
 
 To synchronize my samba source trees I use the following Makefile


@@ -266,7 +266,7 @@ quote(      get:nl()
       sync: get put)
 
 this allows me to sync with a CVS directory at the other end of the
       sync: get put)
 
 this allows me to sync with a CVS directory at the other end of the

-link. I then do cvs operations on the remote machine, which saves a
+connection. I then do cvs operations on the remote machine, which saves a

 lot of time as the remote cvs protocol isn't very efficient.
 
 I mirror a directory between my "old" and "new" ftp sites with the
 lot of time as the remote cvs protocol isn't very efficient.
 
 I mirror a directory between my "old" and "new" ftp sites with the


@@ -654,25 +654,6 @@ Finally, any file is ignored if it is in the same directory as a
 .cvsignore file and matches one of the patterns listed therein.  See
 the bf(cvs(1)) manual for more information.
 
 .cvsignore file and matches one of the patterns listed therein.  See
 the bf(cvs(1)) manual for more information.
 

-dit(bf(--csum-length=LENGTH)) By default the primary checksum used in
-rsync is a very strong 16 byte MD4 checksum. In most cases you will
-find that a truncated version of this checksum is quite efficient, and
-this will decrease the size of the checksum data sent over the link,
-making things faster. 
-
-You can choose the number of bytes in the truncated checksum using the
---csum-length option. Any value less than or equal to 16 is valid.
-
-Note that if you use this option then you run the risk of ending up
-with an incorrect target file. The risk with a value of 16 is
-microscopic and can be safely ignored (the universe will probably end
-before it fails) but with smaller values the risk is higher.
-
-Current versions of rsync actually use an adaptive algorithm for the
-checksum length by default, using a 16 byte file checksum to determine
-if a 2nd pass is required with a longer block checksum. Only use this
-option if you have read the source code and know what you are doing.
-

 dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a
 scratch directory when creating temporary copies of the files
 transferred on the receiving side.  The default behavior is to create
 dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a
 scratch directory when creating temporary copies of the files
 transferred on the receiving side.  The default behavior is to create


@@ -698,7 +679,7 @@ linked.
 
 dit(bf(-z, --compress)) With this option, rsync compresses any data from
 the files that it sends to the destination machine.  This
 
 dit(bf(-z, --compress)) With this option, rsync compresses any data from
 the files that it sends to the destination machine.  This

-option is useful on slow links.  The compression method used is the
+option is useful on slow connections.  The compression method used is the

 same method that gzip uses.
 
 Note this this option typically achieves better compression ratios
 same method that gzip uses.
 
 Note this this option typically achieves better compression ratios