bug-gnu-arch
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnu-arch] [bug #5331] tagging regexps not composable from mulitple


From: nobody
Subject: [Bug-gnu-arch] [bug #5331] tagging regexps not composable from mulitple entries
Date: Sat, 08 Nov 2003 15:52:25 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20031010 Mozilla Firebird/0.6.1 StumbleUpon/1.76

=================== BUG #5331: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5331&group_id=4899

Changes by: Robert Collins <address@hidden>
Date: Sat 11/08/2003 at 20:52 (GMT)

------------------ Additional Follow-up Comments ----------------------------
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 address@hidden/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.



=================== BUG #5331: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: GNU arch -- a revision control 
system
Submitted on: Tue 09/16/2003 at 05:06
Category:  tla                        Severity:  5 - Major                  
Bug Group:  small feature idea        Resolution:  None                     
Status:  Open                         Release:                              
Fixed Release:                        Merge Request?:  None                 
Your Archive Name:                    Your Archive Location:                
Assigned to:  None                    

Summary:  tagging regexps not composable from mulitple entries

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.





Follow-up Comments
*******************

-------------------------------------------------------
Date: Sat 11/08/2003 at 20:52       By: robertc
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 address@hidden/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.

-------------------------------------------------------
Date: Sat 11/08/2003 at 14:50       By: None
Eh?  The "fully specified" regexps become just a special case of only one 
regexp given.

-------------------------------------------------------
Date: Sat 11/08/2003 at 11:34       By: robertc
the patches look reasonable.... but what about backwards compatability with 
fully specified regexes? There's no explicit provision for that.

-------------------------------------------------------
Date: Sun 10/12/2003 at 18:12       By: walters
This is now implemented in my archive:

address@hidden http://arch.verbum.org/arch



See patch-38 and patch-39.






CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
address@hidden             | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5331&group_id=4899

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]