rsync - May 2022 - Problem with file exclusion pattern

On Sat, Apr 30, 2022 at 3:33 PM H wrote:
> rsync -vHrltDium -c --chmod=Du+rwx,go-rwx,Fu+rw,go-rw --no-perms --stats
> --include='*' --include='*/' --exclude='*.~lock*'
--exclude='*' -e "ssh -y
> -p 22" ~/test/ someone at 1.2.3.4:~/test
>
See the latest manpage's filter-rules section
<https://download.samba.org/pub/rsync/rsync.1#FILTER_RULES> an easy way to
debug where filtering is going wrong. Doing that would show you that
everything in your transfer is being matched by the first include option
you used.  This is because (as the 2nd paragraph in the filter section
explains) the first matching pattern is acted upon. A good general rule of
thumb is to move more specific rules prior to more general rules.  However,
in your command above, you only need the one lock-excluding option (since
the default is to include anything that doesn't match any of your rules)
and not any of the other include/exclude options.

..wayne..
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20220502/aa793dfa/attachment.htm>

On May 3, 2022 2:16:58 AM EDT, Wayne Davison <wayne at opencoder.net>
wrote:
>On Sat, Apr 30, 2022 at 3:33 PM H wrote:
>
>> rsync -vHrltDium -c --chmod=Du+rwx,go-rwx,Fu+rw,go-rw --no-perms
>--stats
>> --include='*' --include='*/'
--exclude='*.~lock*' --exclude='*' -e
>"ssh -y
>> -p 22" ~/test/ someone at 1.2.3.4:~/test
>>
>
>See the latest manpage's filter-rules section
><https://download.samba.org/pub/rsync/rsync.1#FILTER_RULES> an easy
way
>to
>debug where filtering is going wrong. Doing that would show you that
>everything in your transfer is being matched by the first include
>option
>you used.  This is because (as the 2nd paragraph in the filter section
>explains) the first matching pattern is acted upon. A good general rule
>of
>thumb is to move more specific rules prior to more general rules. 
>However,
>in your command above, you only need the one lock-excluding option
>(since
>the default is to include anything that doesn't match any of your
>rules)
>and not any of the other include/exclude options.
>
>..wayne..
Thank you, I will look at the reference. However, would I not still need
--include='*/'  since I want it to recourse into all subdirectories?