On Thu, 23 Feb 2017 18:07:20 + David Epstein wrote:
> I will try the modification
> rsync --dry-run -avi --delete --filter 'protect /*’ --filter ‘protect /.*’
> SOURCE/ TARGET/
The 'protect /.*’ is useless: unlike the shell, rsync interprets *
simply as a path component, regardless thus
On Fri, 24 Feb 2017 07:51:56 +0100 francis.montag...@inria.fr wrote:
>> Unfortunately, the output from —dry-run is still likely to be
>> sufficiently extensive that looking over it won’t be a completely
>> certain test.
> Then redirect to a file and grep deleting in this file.
Given the
Thanks for the helpful advice.
In view of the conflicting advice from Joe and Kevin I tried creating a couple
of very small directories test1 and test2, to see what happens when the rsync
command
rsync -avi —dry-run test1/ test2/
is given. I was pleased to see that —dry-run does explicitly say
This is looking good and very helpful to an rsync novice. I will try the
modification
rsync --dry-run -avi --delete --filter 'protect /*’ --filter ‘protect /.*’
SOURCE/ TARGET/
and see what it produces. I do have a number of directories and files beginning
with a dot in TARGET and these need
Hi.
On Thu, 23 Feb 2017 11:07:16 -0500 Kevin Korb wrote:
> I hate to say it because it goes against my normal advice but this is
> one instance where using a * in the source parameter would help...
I totally agree.
I thing that using a protect filter achieves this goal (without using
a *
Either solution should work fine. Your dry run results should be the same.
-v and -i are only output modifying options they don't actually change
the way that rsync works. The extra string there is explained in the
--itemize-changes section of the man page but that particular one means
that the
