Re: Preserving the ability to have both SHA1 and SHA256 signatures

From: Stefan Moch <stefanmoch@mail.de>
Date: May 8, 2021, 10:11 UTC
Message-ID: <f4f782c4-3adc-8c1c-428d-8037426fc475@mail.de>
In-Reply-To: <609645cb11f72_1fc6d208ee@natae.notmuch>

Felipe Contreras wrote:

Show 12 quoted lines

> Junio C Hamano wrote:
>> Christian Couder <christian.couder@gmail.com> writes:
>>> (Not sure why, but, when using "Reply to all" in Gmail, it doesn't
>>> actually reply to you (or Cc you), only to the mailing list. I had to
>>> manually add your email back.)
>>
>> I am sure why.  DWH, please do not use mail-follow-up-to when
>> working with this list.  It is rude and wastes people's time (like
>> the practice just did by stealing time from Christian).
> 
> I agree with this, but shouldn't this be written in some kind of mail
> etiquiette guideline? Along with a rationale.

Good idea to write this down. How to use the mailing list is only sparsely documented. The following files talk about sending to the mailing list:

 1. README.md
 2. Documentation/SubmittingPatches
 3. Documentation/MyFirstContribution.txt
 4. MaintNotes (in Junio's “todo” branch, sent out to the list from
    time to time as “A note from the maintainer”)

2, 3 and 4 mention sending Cc to everyone involved.

2 is about new messages.

3 and 4 specifically talk about keeping everyone in Cc: in replies. Both in the context of “you don't have to be subscribed and you don't need to ask for Cc:”.

Please also note, that mutt sets the “Mail-Followup-To:” header by default for sending to known mailing lists, unless “followup_to” is set to “no”. Whether or not it removes the sender address in this header depends on the list address to be known to be subscribed to or simply known to be a mailing list. It also does not set this header if no recipient address is known as a mailing list.

http://www.mutt.org/doc/manual/#followup-to http://www.mutt.org/doc/manual/#using-lists