include/exclude ?

[Dave Dykstra]

On Fri, Nov 30, 2001 at 03:18:16PM -0700, tim.conway at philips.com wrote:
> You're right.  the order dependency actually lets you create very complex 
> include/exclude rules.  for each item, each --include and --exclude is 
> evaluated in commandline order, until the item has either passed all the 
> tests, and is thus included, or has been excluded, at which point 
> evaluation restarts with the next item.  if you --exclude=* first, every 
> file gets excluded right away, and never gets checked to see if it matches 
> --include=an* .
> Group:  That's a correct synopsis of the behaviour, isn't it?  If not, 
> don't let my error stand.


Correct except that I would say that it has "gone past" all the tests
rather than "has passed".  Saying "has passed" makes it sound like it
matched all the patterns when actually you mean that it didn't match any of
the patterns.

- Dave