git: eb28fee24e - handbook: document new commit message mailing lists

[Philip Paeps]

On 2020-12-15 13:32:49 (+0800), Warner Losh wrote:

> On Mon, Dec 14, 2020, 10:19 PM Philip Paeps <philip at freebsd.org> 
> wrote:
>
>> On 2020-12-14 14:06:43 (+0800), Guangyuan Yang wrote:
>>> +      <para><emphasis>Commit message lists:</emphasis> The 
>>> following
>>> +     lists are for people interested in seeing the log messages for
>>> +     changes to various areas of the source tree.  They are
>>> +     <emphasis>Read-Only</emphasis> lists and should not have mail
>>> +     sent to them.</para>
>>
>> The dev-commits-* lists are not read-only.  All subscribers can post 
>> to
>> them.
>
> I'd love to change things so they are and all follow ups go to a new 
> list,
> maybe dev-commits-discuss....

I don't think this is practical.

It's trivial to set a Reply-To: header to a -discuss list, but Reply-To 
takes either zero or one address.  If the committer being replied to 
doesn't subscribe to the -discuss list, that's not great.  We could add 
-discuss to the To: line, and reply-all will hit that list too, but 
unless folks manually remove the read-only list, they'll get a bounce.

In my experience, discussions on our commit mailing lists are usually 
short ... and when they're not short, they should be (and usually/often 
are) moved to more relevant discussion lists (e.g. arch).

I think trying to add -discuss lists will create more problems than it 
solves.  Discussions will become more fragmented (not less) and we'll 
have a hard time managing people's expectations with respect to what 
"reply" means in specific mail clients.

Philip

-- 
Philip Paeps
Senior Reality Engineer
Alternative Enterprises