git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: cover letter cc's [was: [PATCH 60/67] hw/s390x: add include directory headers]

From
PMPeter Maydell <peter.maydell@linaro.org>
Date
May 4, 2018, 13:32 UTC
Message-ID
<CAFEAcA_xZZ5=oa-rA0=qh2-wxrt14KqH38rdg_OVLrqoTfzA9Q@mail.gmail.com>
In-Reply-To
<20180504152658.3537707a.cohuck@redhat.com>
On 4 May 2018 at 14:26, Cornelia Huck <cohuck@redhat.com> wrote:
Show 8 quoted lines
> On Fri, 4 May 2018 08:07:53 -0500
> Eric Blake <eblake@redhat.com> wrote:
>> On the other hand, cc'ing all recipients for a largely mechanical patch
>> series that was split into 67 parts, in part because it touches so many
>> different maintainers' areas, may make the cover letter have so many
>> recipients that various mail gateways start rejecting it as potential spam.
>
> Yes, large cross-subsystem patch series make this painful.

My solution is to either (a) avoid them or (b) not bother cc'ing people (except people I think might be interested in reviewing cross-subsystem patchsets like Eric ;-))...

thanks -- PMM

Previous: Cornelia HuckNext: Michael S. Tsirkin
Message 3 of 4 in “cover letter cc's [was: [PATCH 60/67] hw/s390x: add include directory headers]”
  1. Eric BlakeMay 4, 2018
  2. Cornelia HuckMay 4, 2018
  3. Peter MaydellMay 4, 2018
  4. Michael S. TsirkinMay 4, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.