-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Menschel writes: > Hello Justin, > > Monday, August 1, 2005, 6:12:16 PM, you wrote: > > >> > - - having to rename the rules is a bit of a mess. not sure > >> > if there is a good way to fix that though > >> > >> Do you mean simply categorizing the names, or the rights to rename? > > JM> no -- the problem is that a rule that comes in as "GREAT_RULE" may come > JM> out the other end as "MID_INVALID_BAT_4", and there's no way to track the > JM> rule renames from end to end, without following it slowly back > JM> through SVN history (which is hard work). > > JM> naming isn't really much of a big deal but it'd be nice to have some way > JM> to keep track of that. (not that I can think of it.) > > The method we sometimes use in SARE is to add comment lines to the > rules file, eg: > > header SARE_SUB_FREE_PRES Subject =~ /(?!free pres[es])free pres./i > describe SARE_SUB_FREE_PRES subject has likely spammer phrase or word > score SARE_SUB_FREE_PRES 1.322 > #ham SARE_SUB_FREE_PRES "free press" www.freepress.net, free > presentation > #hist SARE_SUB_FREE_PRES From 88_FVGT_subject.cf FS_FREE_PRES May 1 > 2004 > > I don't see any reason not to use these comment lines (in whatever > format the project and/or devs choose) and to keep them with rules as > they migrate from submission to test to production. yeah, agreed. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFC8RXoMJF5cimLx9ARArGVAJ4t7StzFI/3N1IMBZzk51Ak1Wl+mACbBC3D Z5CSmthAEIJzOxAgiqMQd3Y= =CCoR -----END PGP SIGNATURE-----
