From: Matt McCutchen Date: Mon, 3 Nov 2008 01:46:08 +0000 (-0500) Subject: The protect filter automatically added with --backup is not perishable X-Git-Tag: v3.0.5pre2~14 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6767ca617b8cf87feda0298db410473923889abf;p=thirdparty%2Frsync.git The protect filter automatically added with --backup is not perishable (see f41152d39396f0672a97268739c333537579404a), so remove the inaccurate "p" from the man page. Noticed by Jacob Balazer: http://lists.samba.org/archive/rsync/2008-November/022022.html --- diff --git a/rsync.yo b/rsync.yo index 0cf99da5..fe6db19d 100644 --- a/rsync.yo +++ b/rsync.yo @@ -671,7 +671,7 @@ Note that if you don't specify bf(--backup-dir), (1) the bf(--omit-dir-times) option will be implied, and (2) if bf(--delete) is also in effect (without bf(--delete-excluded)), rsync will add a "protect" filter-rule for the backup suffix to the end of all your existing excludes -(e.g. bf(-f "Pp *~")). This will prevent previously backed-up files from being +(e.g. bf(-f "P *~")). This will prevent previously backed-up files from being deleted. Note that if you are supplying your own filter rules, you may need to manually insert your own exclude/protect rule somewhere higher up in the list so that it has a high enough priority to be effective (e.g., if