Expanding the include/exclude options

Ben Escoto bescoto@stanford.edu
Sun, 31 Mar 2002 04:51:13 -0800

Content-Type: text/plain; charset=us-ascii

>>>>> "DB" == Donovan Baarda <abo@minkirri.apana.org.au>
>>>>> wrote the following on Sat, 30 Mar 2002 19:53:54 +1100

  DB> IMHO there is some benefits in just adopting rsync's
  DB> syntax... it saves on documentation :-)

  DB> But if you dont, then you can do just about anything, including
  DB> things like;

  DB> --select '+/home/**,-**.bak' --select '+/home/** -**.bak'
  DB> --select '+/home/**' --select '-**.bak' --include '/home/**'
  DB> --exclude '**.bak' --select '["+/home/**","-**.bak"]'

Yeah, now that I think about it rsync seems to have a pretty good
system (except maybe for the implicit scanning/including stuff they
didn't implement).  One sticky point is that rdiff-backup's --exclude
syntax has been different from rsync's.  Ideally I think
rdiff-backup's --include/exclude should use the ** notation, and there
should be a separate --exclude-regexp for perl/python style regular
expressions, but this would break some uses of the old --exclude..

Ben Escoto

Content-Type: application/pgp-signature

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.5 01/15/2001