Re: Help with complicated heirarchy exclude syntax

2007-12-25 Thread reader
Matt McCutchen <[EMAIL PROTECTED]> writes: > Then maybe you want to take only entirely numeric files (the exact > opposite of your original scenario) rather than all files except > entirely alphabetic ones. To do that, you should replace > --include='/nntp/**[!a-zA-Z]*' --exclude='/nntp/**' with

Re: Help with complicated heirarchy exclude syntax

2007-12-25 Thread Matt McCutchen
On Tue, 2007-12-25 at 15:52 -0600, [EMAIL PROTECTED] wrote: > None of these seem to get to the wanted files: > > rsync -navv --prune-empty-dirs --exclude='/nntp/**/' \ > --include='/nntp/**[!a-zA-Z]*' --exclude='/nntp/**' \ > ~/projects/backup/rsync/nntp ./here/ The first filter needs t

Re: Help with complicated heirarchy exclude syntax

2007-12-25 Thread reader
Matt McCutchen <[EMAIL PROTECTED]> writes: [...] >> I've tried lots of combination of slashes and ** but it looks to me >> like those shown above should work. > > By analogy to the other case, those filter rules should exclude files > whose names are entirely alphabetic, and they seem to be doin

Re: Help with complicated heirarchy exclude syntax

2007-12-25 Thread Matt McCutchen
On Tue, 2007-12-25 at 11:08 -0600, [EMAIL PROTECTED] wrote: >--include='/nntp/**[!a-zA-Z]*' --exclude='/nntp/**' > (run in dry run mode to study the output): :) > rsync -navv--include='/nntp/**[!a-zA-Z]*' \ > --exclude='/nntp/**' > ~/projects/backup/rsync/nntp ./

Re: Help with complicated heirarchy exclude syntax

2007-12-25 Thread reader
[EMAIL PROTECTED] writes: > Matt McCutchen <[EMAIL PROTECTED]> writes: > >> To get the rules to apply only in ~/News, anchor the patterns and use >> the ** syntax to match anything below ~/News. The patterns are matched >> against files' full paths from ~, but the first pattern accepts a >> non-n

Re: Help with complicated heirarchy exclude syntax

2007-12-23 Thread Matt McCutchen
On Sat, 2007-12-22 at 17:02 -0600, [EMAIL PROTECTED] wrote: > One further aspect of this that would be nice to solve too, is that > using that technique in this case means that rsync has to check > something like 550,000 (literally) messages to get thru a sync. > > That number will dwindle to a fr

Re: Help with complicated heirarchy exclude syntax

2007-12-22 Thread reader
Matt McCutchen <[EMAIL PROTECTED]> writes: > To get the rules to apply only in ~/News, anchor the patterns and use > the ** syntax to match anything below ~/News. The patterns are matched > against files' full paths from ~, but the first pattern accepts a > non-numeric character only in the basen

Re: Help with complicated heirarchy exclude syntax

2007-12-22 Thread Matt McCutchen
On Sat, 2007-12-22 at 10:09 -0600, [EMAIL PROTECTED] wrote: > Further, how would I define files with numbers for names? > As I understand it, exclude files do not understand regular > expressions. Correct, exclude patterns are globs, and there's no glob that matches files whose names consist enti

Help with complicated heirarchy exclude syntax

2007-12-22 Thread reader
I want rsync to do this: Backup all files under ~/, except in some cases. When rsync gets to ~/News, which has an extensive, fluctuating and deep heirarchy of directories under it. An example might be: News/agent/nntp/news.gmane.org/gmane/comp/lang/perl/beginners/ I want to skip any files th