Re: Commitinfo behaviour

2001-01-26 Thread Derek R. Price
Laine Stump wrote: Do this instead: ^bbb script1 . ^aaa script2 . "^" makes sure that the "bbb" or "aaa" is at the beginning of the directory name. Note that the "/*" isn't doing what you think - it's matching "0 or more '/' characters". Remember, these are *real* regexes,

Commitinfo behaviour

2001-01-25 Thread Chris Cameron
I know that commitinfo takes regular expressions to determine which script to run on each part of the repository. I've always (assumed I guess) thought that the regex started from CVSROOT. I've just observed behaviour which doesn't match this! Can anyone tell me how this is meant to work

RE: Commitinfo behaviour

2001-01-25 Thread Jerry Nairn
You're missing part of the expression, "^". This should be: ^bbb/* script1 . You see it in all of the examples in the manual, so maybe you just overlooked it. The regular expression could just as easily match suffixes, like *.doc script_for_doc_files Jerry From: Chris Cameron

Re: Commitinfo behaviour

2001-01-25 Thread Laine Stump
Chris Cameron [EMAIL PROTECTED] writes: I know that commitinfo takes regular expressions to determine which script to run on each part of the repository. I've always (assumed I guess) thought that the regex started from CVSROOT. I've just observed behaviour which doesn't match this!

RE: Commitinfo behaviour

2001-01-25 Thread Jeremy A. Mates
On Thu, 25 Jan 2001, Jerry Nairn wrote: You see it in all of the examples in the manual, so maybe you just overlooked it. The regular expression could just as easily match suffixes, like *.doc script_for_doc_files Suffixes on module (directory) names, yes. However, you (well, okay, I)