Moving patches traffic to a another list?
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Fri Mar 27 12:11:56 UTC 2020
On 3/27/20 1:52 AM, Augie Fackler wrote:
>
>
>> On Mar 26, 2020, at 7:33 PM, Martin von Zweigbergk <martinvonz at google.com> wrote:
>>
>>
>>
>> On Thu, Mar 26, 2020 at 4:03 PM Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
>>
>>
>> On 3/26/20 8:56 PM, Martin von Zweigbergk via Mercurial-devel wrote:
>>> And we add all existing subscribers of mercurial-devel@ to the new one,
>>> I hope?
>>
>> Can you explain why you would?. My original idea was for devs to opt-in
>> to receive all the phabricator traffic.
>>
>> Because they are currently getting those emails. It was mostly a selfish request (I want to continue to get the emails).
>>
>>
>> Registering people to a verbose -new- mailing list without their consent
>> does not feels right to me. Especially because it is unlikely they would
>> have filter setup for it. In addition I fear that explicitly keeping
>> thousands of people subscribe to the phabricator verbosity would be
>> counter productive since the goal is send a clear sign that the
>> signal/noise ratio is better and get some of these people to pay
>> attention again.
>>
>> Makes sense.
>
>
> Okay, what do you want the new list named? I think I can create it easily enough and set it to moderated, and then we can put only the phabricator from-address in the allow list.
I am not sure.
mercurial-patches@ come to mind, but that would be misleading since
normal patch will still go to mercurial-devel at . So maybe mercurial-phab@
or mercurial-notificiation@? Mercurial-phab@ is not great, but is pretty
clear, so that the best I can think of for now.
What do you think.
--
Pierre-Yves David
More information about the Mercurial-devel
mailing list