owner 414636 ! found 414636 3.0.0~pre9-1 thanks The 3, previously-reported typos are all fixed in rsync/experimental, but I just noticed another one which still exists.
--- /usr/share/man/man1/rsync.1.gz +++ /tmp/rsync1.gz.11637 2008-02-17 17:09:32.000000000 -0500 @@ -1,4 +1,4 @@ -.TH "rsync" "1" "10 Feb 2008" "" "" +.TH "rsync" "1" "17 Feb 2008" "" "" .SH "NAME" rsync \(em a fast, versatile, remote (and local) file-copying tool .SH "SYNOPSIS" @@ -1648,7 +1648,7 @@ .IP This option is most often used when the receiving disk partition does not have enough free space to hold a copy of the largest file in the transfer. -In this case (i.e. when the scratch directory in on a different disk +In this case (i.e. when the scratch directory is on a different disk partition), rsync will not be able to rename each received temporary file over the top of the associated destination file, but instead must copy it into place. Rsync does this by copying the file over the top of the
--- /usr/share/man/man1/rsync.1.gz +++ /tmp/rsync1.gz.11637 2008-02-17 17:09:32.000000000 -0500 @@ -1,4 +1,4 @@ -.TH "rsync" "1" "10 Feb 2008" "" "" +.TH "rsync" "1" "17 Feb 2008" "" "" .SH "NAME" rsync \(em a fast, versatile, remote (and local) file-copying tool .SH "SYNOPSIS" @@ -1648,7 +1648,7 @@ .IP This option is most often used when the receiving disk partition does not have enough free space to hold a copy of the largest file in the transfer. -In this case (i.e. when the scratch directory in on a different disk +In this case (i.e. when the scratch directory is on a different disk partition), rsync will not be able to rename each received temporary file over the top of the associated destination file, but instead must copy it into place. Rsync does this by copying the file over the top of the
