"Every time a message goes from X to Y, suddenly Y does (thing) a day later"
And then investigate from there.
561 karma · joined September 21, 2020
"Every time a message goes from X to Y, suddenly Y does (thing) a day later"
And then investigate from there.
They refurbished all the bus stops that still had stickers for it a few years ago.
At work we have to deal with parsing the".msg" abominations Outlook _actually_ exports.
Being cautious here means "it's better to assign a CVE when it's not a vulnerability, than to NOT assign a CVE when it's actually a vulnerability"
Probably because it uses the same 303's and 909's :)
I've had my share of weird issues in Chrome because they enabled an "experiment" of some kind.
Those really show why those commit messages are useful to figure out why things were done the way they were ("what the dev was thinking"). This is especially useful if some kind of bug is found 2 years later and someone who wasn't involved in the original change needs to fix it.
It's mentioned in Eben Upton's blog post (linked from the announcement):
https://www.raspberrypi.com/news/introducing-raspberry-pi-5/