Disturbing that someone that fixes a bug in this space doesn't check the most advanced implementation
-
-
Replying to @lazytyped @bsdaemon and
Why on earth would someone think "hm, I found a kernel bug, let me check just in case grsec also has the fix"? That's ridiculous.
1 reply 0 retweets 0 likes -
Because understanding prior work is crazy important in this field.
1 reply 0 retweets 0 likes -
Replying to @lazytyped @bsdaemon and
Nobody cares about "prior work" for a one-line bugfix. Seriously, this is *trivial stuff*.
1 reply 0 retweets 0 likes -
Most critical fixes are small. Number of lines is not a measure.
1 reply 0 retweets 0 likes -
Replying to @lazytyped @bsdaemon and
Number of lines is not a measure of criticality. It *is* a measure of originality. A one-line fix can be rediscovered many times.
1 reply 0 retweets 0 likes -
Everything can be discovered independently, that's not the point.
1 reply 0 retweets 0 likes -
Replying to @lazytyped @bsdaemon and
The point is that if it *is* then no credit is expected or required, and that is *likely* for changes like this.
1 reply 0 retweets 0 likes -
No. The point is that for a (security) fix, if it was already fixed, it's just natural to give credit when pointed out.
1 reply 0 retweets 0 likes -
Replying to @lazytyped @bsdaemon and
1) I disagree, 2) the problem wasn't refusing credit after it was pointed out; Spender got angry that there was no *initial* credit.
2 replies 0 retweets 0 likes
But it's literally impossible to give initial credit when you're unaware it was already fixed. Spender just assumed it was copied.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.