Bug#414636: rsync: s/in/is/ rsync.1

Paul Slootman paul+rsync at wurtel.net
Mon Feb 18 11:41:37 GMT 2008


>From a Debian bug report:

On Sun 17 Feb 2008, Justin Pryzby wrote:
> 
> 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
> @@ -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
> 

Or, in rsync.yo context:

--- rsync.yo.orig	2008-02-11 05:16:25.000000000 +0100
+++ rsync.yo	2008-02-18 12:40:58.934511231 +0100
@@ -1432,7 +1432,7 @@
 
 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


Paul Slootman


More information about the rsync mailing list