Hello George,

Thursday, February 17, 2005, 8:16:21 AM, you wrote:

>>Fair enough.  In this most recent publication of updates to the
>>70_sare_header*.cf family, 40 rules were added, and 50 rules were
>>moved from one file to another, including 8 or 9 that were moved from
>>various files to the archive file.
>>
>>How would you structure a change history for those changes?

GG> Are the files in cvs? I would suggest using the log keyword: ...

Nope, no cvs, no svn. They're manually maintained, with generally only
one SARE Ninja maintaining any single rules files.

GG> #@@# $Log: README,v $
GG> #@@# Revision 1.7  2005/02/17 15:42:54  geo
GG> #@@#
GG> #@@# Changed MSGID_WRONG due to high false negatives
GG> #@@# Added a log keyword. And noted changes made to this file.
GG> #@@# Added BROKE_SPAMWARE from Adam
GG> #@@# Added IDIOT_SPAMER from Jim Hoan
GG> #@@# Added FREE_MONEY from Joe John
GG> #@@# Added TEN_QUESTIONS from 70_sare_freefriends.cf
GG> #@@# Moved MAGIC_WORKS to 70_sare_oem.cf
GG> #@@# Removed TRIES_HARD due to false positives

And as I said, the equivalent change log for this last update to the
header* files would have been close to 100 lines long. Is that what
you would like to see?

Bob Menschel



Reply via email to