3 ms·
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 co
by 0x0 10y ago
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.
- cm3 10y agoFair point, though LKML is very high volume, so not as much of a big deal as one might think.
- cm3 10y ago> 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.
- ubernostrum 10y agoBlasting 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.
- digi_owl 10y agoOr a initial email going "heads up, big patch set coming through!", with the patch set as replies to that one.
- cm3 10y agoThat's usually what happens with a git formatted patchset that has you draft a patch-0 (aka introduction of the series) email.