Kevin L. Mitchell writes: >> <Entrope> things i forgot to say in my email: >> <Entrope> glines with no listed lifetime have lifetime == expiration >> <Entrope> and, as is (mostly) done now, incoming glines with no listed >> lastmod are treated as being more recent than any existing gline >> <Entrope> and i'd suggest that we don't keep a flag for deactivated >> glines: if we get a [EMAIL PROTECTED], we set the expiration (but not >> lifetime) to be at or before the current time > > I'd considered that as well, but I'm wondering if we want to allow a > G-line to be deactivated, then reactivated with the same options it had > before. If we reset the expiration time like this, my command syntax > will require us to respecify both the expiration time and the G-line > reason...
That's a good point. I had not considered that kind of use. > BTW, is this a change we should stick into .13, or are you comfortable > with development of this in .12.pre10? The trie code should be .13-only, but that is orthogonal to the changes you propose. If you have no objections, I would rather make a .12.10 release before we start reworking the existing G-line logic. Entrope _______________________________________________ Coder-com mailing list Coder-com@undernet.org http://undernet.sbg.org/mailman/listinfo/coder-com
