On Fri, Apr 24, 2020 at 07:43:03AM +0100, Lee Jones wrote: > A great deal of mailing lists contain numerous protections against > things like flooding and spamming. One of those protections is a > check for "Too many recipients to the message". Most of the time this > simply requires moderator intervention by way of review and approval, > but this ultimately depends on the ML's configuration. > > The first thing to ascertain is why your recipients list is so large. > Have you added every reviewer, subsystem-maintainer, maintainer and > contributor suggested by get-maintainer.pl? If so, consider pruning > that a little. Contributors do not tend to care about subsequent > changes to a file. As someone who receives a lot of patches, I tend > to get fed-up when receiving patches simply because I made a change X > years ago. Stick to listed maintainers/reviewers in the first > instance and see how far that takes you. Thank you for the detailed reply. I did this in the first few patchsets and then when a few patches didn't get any attention, expanded the audience thus. Still, around 50% of the patches in this series remain unreviewed by anyone. > If your recipients list is as succinct as reasonably possible, maybe > just accept that every version isn't going to be archived by every > ML. It's still much more useful for the correct people to have > visibility into the set than for it to be archived multiple times. Thank you, will prune the list and remove past contributors from the Cc-list and add all parties to all patches. Thank you. Guru Das. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
