On Tue, Nov 15, 2022 at 01:25:04PM +0000, Nick Alcock wrote: > (I'm also a bit miffed because people are worrying about 10K of > overhead at the same time as a patch is going in adding half a meg ;) You are missing that the reason why your patch lacks much traction is it lacks a clear *use* case. It has nothing to do with space. The cover letter can be really summarized in a condensed way to get the point accross to just include the text on your first paragraph you had at Plumbers: https://lpc.events/event/16/contributions/1379/ This gets the point accross well. The rest of the cover letter is just pure noise and gets me lost. But for instance, when I reviewed the patch for adding ranges, your cover letter describes the *justification*, the *why* to do that, but the patch does not at all. Please make sure that your commits describe *why* clearly. Please get a bit of help from your team to condense to the cover letter to only include what is needed if someone is reading the patchset for the very first time. And then users.. we need users clearly documented, who the heck is using this or wants this / is going to use it and why. Luis
