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

Re: [BUG] suppress-cc does not support multiple keywords

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Aug 13, 2025, 06:34 UTC
Message-ID
<CAPig+cTvCLU3u5y23HSrbxovs8cjcJdOUj0e1G9Rg4F1AP0jAg@mail.gmail.com>
In-Reply-To
<CAOZdJXWaC2U_YrwuDcA0x3iUeF_uJ658a93cTfdLftEXYRB52Q@mail.gmail.com>
On Tue, Aug 12, 2025 at 8:06 PM Timur Tabi <timur@kernel.org> wrote:
Show 5 quoted lines
> I hope this isn't just some user error on my part, but whenever I use
> the --suppress-cc option, and I specify more than one keyword (e.g.
> --suppress-cc=author,self ), git complains that it doesn't recognize
> the keyword.  It seems that it treats all of the comma-separated
> keywords as one big keyword with commas in it.

It's probably a case of user error. As far as I can see, the documentation[*] does not in any way suggest that --suppress-cc accepts a comma-separated list of categories to suppress.

> I was able to work around the problem by specifying --suppress-cc
> multiple times, once for each keyword.

Indeed, consulting the source code, this behavior appears to be intentional. If there is any "bug", it's that the documentation does state that you can specify --suppress-cc multiple times (even though you obviously can).

[*]: https://git-scm.com/docs/git-send-email#Documentation/git-send-email.txt---suppress-cccategory
Previous: Timur TabiNext: Junio C Hamano
Message 2 of 4 in “[BUG] suppress-cc does not support multiple keywords”
  1. Timur TabiAug 13, 2025
  2. Eric SunshineAug 13, 2025
  3. Junio C HamanoAug 13, 2025
  4. Eric SunshineAug 13, 2025

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.