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

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

From
Eric Blake <eblake@redhat.com>
Date
May 4, 2018, 13:07 UTC
Message-ID
<be79d6dd-beaa-ba6f-2990-b5e91139411b@redhat.com>
In-Reply-To
<20180504091007.55405a6a.cohuck@redhat.com>
[adding a cross-post to the git mailing list]
On 05/04/2018 02:10 AM, Cornelia Huck wrote:
Show 7 quoted lines
> On Thu, 3 May 2018 22:51:40 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
>> This way they are easier to find using standard rules.
>>
>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>> ---
...
> [Goes to find cover letter to figure out what this is all about.
> *Please*, cc: people on the cover letter so they can see immediately
> what this is trying to do!]

Is there an EASY way to make 'git format-patch --cover-letter $commitid' (and git send-email, by extension) automatically search for all cc's any any of the N/M patches, and auto-cc ALL of those recipients on the 0/N cover letter? And if that is not something easily built into git format-patch directly, is it something that can easily be added to sendemail.cccmd? This is not the first time that someone has complained that automatic cc's are not sending the cover letter context to a particular maintainer interested (and auto-cc'd) in only a subset of an overall series.

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.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org
Next: Cornelia Huck
Message 1 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.