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

Re: [PATCH] git-send-email: Cc more people

From
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Date
Apr 19, 2018, 12:35 UTC
Message-ID
<646938104.13100.1524141300699.JavaMail.zimbra@efficios.com>
In-Reply-To
<20180419121024.GD5556@bombadil.infradead.org>
----- On Apr 19, 2018, at 8:10 AM, Matthew Wilcox willy@infradead.org wrote:
Show 27 quoted lines
> On Thu, Apr 19, 2018 at 06:21:42AM +0900, Junio C Hamano wrote:
>> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>> 
>> > But IMO this patch is really lacking a few things before being ready:
>> >
>> > 1. You have no tests for this. See t/t9001-send-email.sh for examples,
>> > ...
>> > 2. Just a few lines down from your quoted hunk we have this:
>> > ... code about $supress_cc{<token>} ...
>> >    Your change should at least describe why those aren't being updated,
>> >    but probably we should add some other command-line option for
>> >    ignoring these wildcards, e.g. --[no-]wildcard-by-cc=reviewed
>> >    --[no-]wildcard-by-cc=seen etc, and we can make --[no-]signed-off-by
>> >    a historical alias for --[no-]wildcard-by-cc=signed-off.
>> > 3. Ditto all the documentation in "man git-send-email" about
>> > ...
>> 
>> Thanks, I agree that 2. (the lack of suppression) is a showstopper.
> 
> I agree with that (and the lack of tests, obviously)
> 
>> I'd further say that these new CC-sources should be disabled by
>> default and made opt-in to avoid surprising existing users.
> 
> But I disagree with this.  The current behaviour is surprising to
> existing users, to the point where people are writing their own scripts
> to replace git send-email (which seems crazy to me).

We could perhaps go with a whitelist approach. The four main match I would be tempted to add are: Acked-by, Reported-by, Reviewed-by, and Tested-by.

My workflow is to initially CC a bunch of relevant maintainers when sending out a patch, and as the Acked, Reviewed and Tested by tags come it, I replace those CC with the relevant tag. I never expected them to stop being CC'd when switching between those categories.

Thanks,
Mathieu
Show 11 quoted lines
> 
>> One thing we also need to be very careful about is that some of the
>> fields may not even have an e-mail address.  We can expect that
>> S-o-b and Cc would be of form "human readable name <email@addre.ss>"
>> by their nature, but it is perfectly fine to write only human
>> readable name without address on random lines like "suggeted-by" and
>> "helped-by".  There needs a way for the end-user to avoid using data
>> found on such lines as if they are valid e-mail addresses.
> 
> I also agree with this.  I'll add some test-cases and make sure we only
> add these if they're valid email addresses.
-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
Previous: Matthew WilcoxNext: Junio C Hamano
Message 7 of 9 in “git-send-email: Cc more people”
  1. git-send-email: Cc more peopleMatthew Wilcox, Apr 18, 2018
  2. Steven RostedtApr 18, 2018
  3. Mathieu DesnoyersApr 18, 2018
  4. Ævar Arnfjörð BjarmasonApr 18, 2018
  5. Junio C HamanoApr 18, 2018
  6. Matthew WilcoxApr 19, 2018
  7. Mathieu DesnoyersApr 19, 2018
  8. Junio C HamanoApr 20, 2018
  9. Mathieu DesnoyersApr 20, 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.