Rsync 2.6.7pre1 is now available

[Paul Slootman]

On Wed 08 Feb 2006, Wayne Davison wrote:

> Rsync version 2.6.7pre1 is now available for release testing.  Please
> give it a try and send email to the regular mailing list with any
> questions, comments, bug reports, etc.

A couple of text improvements / typos that were sent to me...

Paul Slootman


--- rsync-2.6.7pre1.orig/rsync.yo
+++ rsync-2.6.7pre1/rsync.yo
@@ -1014,7 +1018,7 @@
 as it is sent to the destination machine, which reduces the amount of data
 being transmitted -- something that is useful over a slow connection.

-Note this this option typically achieves better compression ratios that can
+Note this this option typically achieves better compression ratios than can
 be achieved by using a compressing remote shell or a compressing transport
 because it takes advantage of the implicit information in the matching data
 blocks that are not explicitly sent over the connection.
@@ -1191,7 +1195,7 @@

 You can also set the partial-dir value the RSYNC_PARTIAL_DIR environment
 variable.  Setting this in the environment does not force bf(--partial) to be
-enabled, but rather it effects where partial files go when bf(--partial) is
+enabled, but rather it affects where partial files go when bf(--partial) is
 specified.  For instance, instead of using bf(--partial-dir=.rsync-tmp)
 along with bf(--progress), you could set RSYNC_PARTIAL_DIR=.rsync-tmp in your
 environment and then just use the bf(-P) option to turn on the use of the
@@ -1268,7 +1272,7 @@
 instead of transferred.  This option is inferred if there is no destination
 specified, so you don't usually need to use it explicitly.  However, it can
 come in handy for a user that wants to avoid the "bf(-r --exclude='/*/*')"
-options that rsync might use as a compatibility kluge when generating a
+options that rsync might use as a compatibility kludge when generating a
 non-recursive listing, or to list the files that are involved in a local
 copy (since the destination path is not optional for a local copy, you
 must specify this option explicitly and still include a destination).
@@ -1593,7 +1597,7 @@
   "- foo + bar" is parsed as two rules (assuming that prefix-parsing wasn't
   also disabled).
   it() You may also specify any of the modifiers for the "+" or "-" rules
-  (below) in order  to have the rules that are read-in from the file
+  (below) in order  to have the rules that are read in from the file
   default to having that modifier set.  For instance, "merge,-/ .excl" would
   treat the contents of .excl as absolute-path excludes,
   while "dir-merge,s .filt" and ":sC" would each make all their
@@ -1654,7 +1658,7 @@

 This will merge the contents of the /home/user/.global-filter file at the
 start of the list and also turns the ".rules" filename into a per-directory
-filter file.  All rules read-in prior to the start of the directory scan
+filter file.  All rules read in prior to the start of the directory scan
 follow the global anchoring rules (i.e. a leading slash matches at the root
 of the transfer).

@@ -2062,7 +2066,7 @@
 
 manpagebugs()

-times are transferred as unix time_t values
+times are transferred as Unix time_t values
 
 When transferring to FAT filesystems rsync may re-sync
 unmodified files.