Re: Commitinfo behaviour

[Laine Stump]

Chris Cameron <address@hidden> 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!  Can anyone tell me how this is meant to work (is 
> it a bug or expected behaviour).  What I saw was:
> 
> commitinfo:
> bbb/* script1 .....
> aaa/* script2 .....

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, not shell pathname wildcards...


> In the working directory was the structure
> aaa/ccc
> aaa/ddd/bbb
> aaa/eee
> 
> During the commit script2 was run in aaa/ccc aaa/ddd and aaa/eee, but 
> sript1 was run in aaa/ddd/bbb!
> 
> 
> ***************************************************************
> Chris Cameron                    Open Telecommunications NZ Ltd
> Product Manager                           IN Product Management
> address@hidden                           P.O.Box 10-388
>       +64 4 495 8403 (DDI)                          The Terrace
> fax:  +64 4 495 8419                                 Wellington
> cell: +64 21 650 680                                New Zealand
> Life, don't talk to me about life ....(Marvin - HHGTTG)
> 
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs