Re: anchoring of patterns for per-directory merge files

2009-11-12 Thread Matt McCutchen
On Wed, 2009-11-11 at 17:14 +, Andy Smith wrote: > I'm extremely confused about anchoring of patterns for per-directory > merge files, as what I see seems to not be the behaviour the > documentation suggests. > > On the receiver side I have rsync version 3.0.3 protocol v

Re: anchoring of patterns for per-directory merge files

2009-11-11 Thread Andy Smith
On Wed, Nov 11, 2009 at 06:12:53PM +, Andy Smith wrote: > "-/ tmp/" works though, and does only exclude exactly what I want. I spoke too soon. For me, "-/ tmp/" works identically to "- tmp/", that is it excludes everything with a "tmp/" directory in it: [sender] hiding directory /data/home/a

Re: anchoring of patterns for per-directory merge files

2009-11-11 Thread Andy Smith
On Wed, Nov 11, 2009 at 05:59:29PM +, Andy Smith wrote: > On Wed, Nov 11, 2009 at 06:43:33PM +0100, Paul Slootman wrote: > > From the manpage: > > > >The following modifiers are accepted after a “+” or “-”: > > > >o A / specifies that the include/exclude rule should be matched

Re: anchoring of patterns for per-directory merge files

2009-11-11 Thread Andy Smith
Hi Paul, On Wed, Nov 11, 2009 at 06:43:33PM +0100, Paul Slootman wrote: > From the manpage: > >The following modifiers are accepted after a “+” or “-”: > >o A / specifies that the include/exclude rule should be matched > against the absolute pathname of the current item

Re: anchoring of patterns for per-directory merge files

2009-11-11 Thread Paul Slootman
On Wed 11 Nov 2009, Andy Smith wrote: > > On the sender, I have in the file "/data/home/andy/.rsync-filter": > > - /tmp/ > > The documentation leads me to believe that this should exclude a > directory called "tmp/" located only in the same directory as the > merge file. What happens is, nothin

anchoring of patterns for per-directory merge files

2009-11-11 Thread Andy Smith
Hi, I'm extremely confused about anchoring of patterns for per-directory merge files, as what I see seems to not be the behaviour the documentation suggests. On the receiver side I have rsync version 3.0.3 protocol version 30. On the sender I have rsync version 2.6.9 protocol versi