Sure, that is the way it normally works. By default everything is
included. Excludes exclude things. Includes are exceptions to includes
that follow.
Note that this can get very complicated. --exclude-from=file.txt makes
things much easier as you can use the +/- syntax to put both includes
On 04/30/2022 08:22 PM, Kevin Korb via rsync wrote:
> Includes override excludes that follow. So, your include of * meant that
> nothing was being excluded. An exclude before any includes isn't affected by
> the includes.
>
> On 4/30/22 20:04, H via rsync wrote:
>> On 04/30/2022 07:56 PM, H via
Includes override excludes that follow. So, your include of * meant
that nothing was being excluded. An exclude before any includes isn't
affected by the includes.
On 4/30/22 20:04, H via rsync wrote:
On 04/30/2022 07:56 PM, H via rsync wrote:
Ah, I was under the impression that all inclus
On 04/30/2022 07:56 PM, H via rsync wrote:
>
> Ah, I was under the impression that all inclusion patterns need to preceed
> the exclusion patterns?
>
>
>
> Forwarded Message
> Subject: Re: Problem with file exclusion pattern
> Date: Sat, 30 Apr 2022 18:49:22 -0400
>
Ah, I was under the impression that all inclusion patterns need to preceed the
exclusion patterns?
Forwarded Message
Subject:Re: Problem with file exclusion pattern
Date: Sat, 30 Apr 2022 18:49:22 -0400
From: Kevin Korb
To: H
Drop the include of * or move
I am running rsync on Linux and have yet to find the appropriate pattern to
exclude files containing '.~lock' as part of the name of files existing in any
directory, ie ~/test and below.
rsync -vHrltDium -c --chmod=Du+rwx,go-rwx,Fu+rw,go-rw --no-perms --stats
--include='*' --include='*/' --excl
