On Thu, 2020-07-02 at 08:42 -0700, Kees Cook wrote: > On Thu, Jul 02, 2020 at 04:23:35PM +0100, Mark Brown wrote: > > On Thu, Jul 02, 2020 at 08:21:40AM -0700, Kees Cook wrote: > > > On Wed, Jul 01, 2020 at 09:39:20PM +0100, Mark Brown wrote: > > > > Please copy maintainers on patches :( > > > Hi! Sorry about that; the CC list was giant, so I had opted for using > > > subsystem mailing lists where possible. > > > > If you're going to err in a direction there I'd err in the direction of > > CCing the people not the list - I only saw this since I was looking for > > something else, I don't normally see stuff in the mailing list folder. > > Yeah, I've gotten conflicting feedback on treewide changes: > - please CC me on only the one patch, I don't want to see everything else > - please CC me on the whole series, I want the full context for the change > > I opted toward "CC me on this series", but then I get stuck when the CC > is giant. I think I may switch back to individual CCs for specific > patches, and point people to lore if they want greater context. (lore > didn't exist before...) IMO: For a patch series that spans multiple subsystems, each patch should always CC any specific subsystem maintainers.. A good trick would be to use the cover letter message-id: and have each individual patch in the series reference the cover letter id below the --- line so any reviewer doesn't have to find the in-reply-to: message id and then reference the lore link. Something like: --- For complete series see: https://lore.kernel.org/r/<cover_letter_message_id>
