You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Karsten Bräckelmann <gu...@rudersport.de> on 2009/09/03 17:33:58 UTC
Rule changes Deadline !?
Bug 6155 comment 21. Deadline for rule changes *today*. :-/
That means midnight UTC, right? Right!?
(a) I still do need to push some rule changes. Won't be able to do that
for another few hours, though.
(b) Scores will be built after all mass-check results are in. Does that
mean, that we can completely drop some of the sandbox rules *after*
mass-check results are in? Or do I have to do that tonight, too?
The reason for this is, that there are still quite a lot of testing
variants, and the final rule-set seriously should contain one of each
set of almost-equivalent variants only.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: Rule changes Deadline !?
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Thu, 2009-09-03 at 17:50 +0200, Karsten Bräckelmann wrote:
> On Thu, 2009-09-03 at 16:40 +0100, Justin Mason wrote:
> > I wasn't thinking midnight - more around 9pm gmt. Also, you can
>
> 23:00 in my timezone +0200, CEST. I should be able to get the rule
> changes in by then.
*phew* OK, /finally/ pushed the most important change. Sorry for the
late hack.
> > include several testing variants and nuke the ones that don't work
> > after the mass checks but before the ga.
Will compile a list of stuff to drop before the GA run.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: Rule changes Deadline !?
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Thu, 2009-09-03 at 16:40 +0100, Justin Mason wrote:
> I wasn't thinking midnight - more around 9pm gmt. Also, you can
23:00 in my timezone +0200, CEST. I should be able to get the rule
changes in by then.
> include several testing variants and nuke the ones that don't work
> after the mass checks but before the ga.
Great. No need to do it tonight then, got some days. :)
> On Thursday, September 3, 2009, Karsten Bräckelmann wrote:
> > Bug 6155 comment 21. Deadline for rule changes *today*. :-/
> >
> > That means midnight UTC, right? Right!?
> >
> > (a) I still do need to push some rule changes. Won't be able to do that
> > for another few hours, though.
> >
> > (b) Scores will be built after all mass-check results are in. Does that
> > mean, that we can completely drop some of the sandbox rules *after*
> > mass-check results are in? Or do I have to do that tonight, too?
> >
> > The reason for this is, that there are still quite a lot of testing
> > variants, and the final rule-set seriously should contain one of each
> > set of almost-equivalent variants only.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: Rule changes Deadline !?
Posted by Justin Mason <jm...@jmason.org>.
I wasn't thinking midnight - more around 9pm gmt. Also, you can
include several testing variants and nuke the ones that don't work
after the mass checks but before the ga.
On Thursday, September 3, 2009, Karsten Bräckelmann
<gu...@rudersport.de> wrote:
> Bug 6155 comment 21. Deadline for rule changes *today*. :-/
>
> That means midnight UTC, right? Right!?
>
> (a) I still do need to push some rule changes. Won't be able to do that
> for another few hours, though.
>
> (b) Scores will be built after all mass-check results are in. Does that
> mean, that we can completely drop some of the sandbox rules *after*
> mass-check results are in? Or do I have to do that tonight, too?
>
> The reason for this is, that there are still quite a lot of testing
> variants, and the final rule-set seriously should contain one of each
> set of almost-equivalent variants only.
>
>
> --
> char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
> main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
> (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
>
>
--
--j.