4 ms·

The response to the bug on the mailing list is disheartening. Report goes "set errno=0 so your error message makes sense". Didn't get a thanks, fixed. Instead

The response to the bug on the mailing list is disheartening. Report goes "set errno=0 so your error message makes sense". Didn't get a thanks, fixed. Instead there's objections on the basis "filesystems shouldn't work like that".

chubot 1y ago
There seem to be a bunch of toxic people on the bash mailing list, and I think many or all of them don't even contribute code The person who responded dismissively later says "I'm just another user." --- Every commit since they started using git in 2009 is attributed to one person: https://cgit.git.savannah.gnu.org/cgit/bash.git/log/ https://cgit.git.savannah.gnu.org/cgit/bash.git/log/ I think occasionally contributed patches are applied, but this is not apparent in source control. I was attacked on the bash mailing list a several years ago, so I don't go there anymore :-)
BenjiWiebe 1y ago
Especially when the man page for readdir() mentions that you should set errno=0 if you want to distinguish errors from end-of-stream. Not like setting errno=0 before calling readdir() is a novel idea...