> --- Comment #4 from Warren Togami <[email protected]> 2011-01-17 22:20:21 UTC
> ---
> This isn't fixed until it is pushed to the sa-update channel.
I don't want to start an edit-war, so I keep the bug in the REOPENED
state. However, I *do* want to clarify that sentence as-is is wrong.
Resolved FIXED means in code.
The equivalent, a bug targeted for $release, is resolved once the code
is in the appropriate branch, and voting has been done if required. It
does not remain open until an actual release.
Lack of the ability to immediately push an update out, or automatic,
periodic updates failing are unrelated bugs. They are not inherently
part of each and every bug concerning rules.
The exception to that rule are dependencies. If you believe a bug is
sufficiently severe to depend on it (the infra being in place, mind you,
again not the actual pushing), then please make the bug reflect that
fact. Raise the severity and/or priority accordingly, and make the bug
"depend on" the relevant bug that also needs to be fixed.
--
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; }}}
