I presume that's walters saying that? I'm going to paraphrase what Tom said to me - login to Savannah.... please. Oh, and when listing where it's available, be sure to include the category--branch--version triplet: guessing is a nuisance.

So yes - you'll end up with
(^(....)$)
for the one regexp specified. Ok, thats good enough - I shouldn't have been reviewing late at night :}.

Merged into rbtcollins@hotmail.com--barch/tla--integration--1.1--patch-6 and patch-7.

Would you like to extend this to support multiple regexps in .arch-inventory files? The patch for that is in my integration branch too.

the patches look reasonable.... but what about backwards compatability with fully specified regexes? There's no explicit provision for that.

It would helpful for maintainability and readability purposes if multiple entries for a category regexp could be built in 'or' clauses from multiple entries, like this:

precious ^pat1$
precious ^pat2$

which would imply:

precious (^pat1$|^pat2$)

This way, various commonly used subpatterns could be grouped together and cut/pasted between various projects.  It's also more easily readable than very long single regexps.