Collin Funk

@bob_zim@infosec.exchange @w8emv@a2mi.social @hyc@mastodon.social @lcamtuf@infosec.exchange The number is a bit misleading. We have ~700 shell/perl scripts, which often times have many test cases. E.g., one script tests that all programs that write to standard output properly diagnose write errors.

@bkuhn@fedi.copyleft.org @mjw@mastodon.nl Ah, I read these posts too fast and didn't see the suggested change was for 'ls' instead of 'ln'. Well there is some related reading anyways if you are interested...

@bkuhn@fedi.copyleft.org @mjw@mastodon.nl There was a relatively long bug report discussing different ways to make this less confusing a few years ago: https://bugs.gnu.org/52115 I think I agree with Bernhard for the most part. Especially that the synopsis of 'ln' is a bit of a mess that we should avoid complicating further.

@bob_zim@infosec.exchange @w8emv@a2mi.social @hyc@mastodon.social Yeah, if you clone coreutils git repository and open the HACKING file at the top level you can scroll to the bottom for instructions.