Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Blasting over 1200 emails to a mailing list with no heads-up appears quite tone-deaf, to put it mildly even if you presume good intentions.

Edit: The impact could be shown in a single email with a diffstat, for example. Complaining about a lack of feedback for such a thing sounds more like complaining about failing to draw others in to a bikeshedding competition.



> The impact could be shown in a single email with a diffstat, for example.

True, and I agree, but not the way stuff is usually done on LKML, thus probably not considered.

In this special case of a huge number of patches it might have been a good idea to present an RFC diffstat first, yes. Actually, I wish github had a .diffstat extension for pull requests, because often that's the first thing I care about before I know if I want to delve into a random big patch.


Blasting over 1200 emails to a mailing list with no heads-up appears quite tone-deaf

Compared to the bits and pieces of LKML I occasionally see, blasting 1200 emails is downright polite.


Or a initial email going "heads up, big patch set coming through!", with the patch set as replies to that one.


That's usually what happens with a git formatted patchset that has you draft a patch-0 (aka introduction of the series) email.


Fair point, though LKML is very high volume, so not as much of a big deal as one might think.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: