Yet another filter question

Kevin Korb kmk at
Thu May 5 01:09:44 UTC 2016

I hate to say anything remotely negative to Wayne but...

That wording from the man page makes almost no sense without the
examples directly after it (and I have read it many times and know what
it is saying).

When I go all RTFM on this topic I usually tell them to 'man rsync',
search for file-will-not-be-found and start reading from that line.
Once you understand the broken and correct examples you can decipher
what the explanation above means.

On 05/04/2016 09:03 PM, Wayne Davison wrote:
> On Tue, May 3, 2016 at 1:07 PM, Christoph Biedl <cbiedl at
> <mailto:cbiedl at>> wrote:
>       + *.git/.git/*
>       - *.git/
> From the man page near the start of the "INCLUDE/EXCLUDE PATTERN RULES"
> section:
>     /Note that, when using the --recursive (-r) option (which is implied
>     by -a), every subcomponent of every path is visited from the top
>     down, so include/exclude patterns get applied recursively to each
>     subcomponent’s full name (e.g. to include "/foo/bar/baz" the
>     subcomponents "/foo" and "/foo/bar" must not be excluded). The
>     exclude patterns actually short-circuit the directory traversal
>     stage when rsync finds the files to send./
> Thus, your latter exclude prevents the first include from ever seeing
> any data that it could match. You'd need to use something more like this:
> + *.git/.git/
> - *.git/*
> ..wayne..

	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at  (work)
	Orlando, Florida		kmk at (personal)
	Web page:
	PGP public key available on web site.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the rsync mailing list