bugGNU arch -- a revision control system - Bugs: bug #5331, tagging regexps not composable...

 
 

bug #5331: tagging regexps not composable from mulitple entries

Submitted by:  None
Submitted on:  Tue 16 Sep 2003 05:06:00 AM UTC  
 
Category: tlaSeverity: 3 - Normal
Item Group: small feature ideaStatus: None
Privacy: PublicOpen/Closed: Open
Release: 
Fixed Release: 
Merge Request?: None
Your Archive Name: 
Your Archive Location: 
Assigned to: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sat 08 Nov 2003 08:52:24 PM UTC, comment #4:

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.

Robert Collins <robertc>
Sat 08 Nov 2003 02:50:35 PM UTC, comment #3:

Eh? The "fully specified" regexps become just a special case of only one regexp given.

Anonymous
Sat 08 Nov 2003 11:34:16 AM UTC, comment #2:

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

Robert Collins <robertc>
Sun 12 Oct 2003 06:12:51 PM UTC, comment #1:

This is now implemented in my archive:
walters@verbum.org--2003 http://arch.verbum.org/arch

See patch-38 and patch-39.

Colin Walters <walters>
Tue 16 Sep 2003 05:06:00 AM UTC, original submission:

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.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

No Changes Have Been Made to This Item

Back to the top


Powered by Savane 3.1-cleanup1