What's wrong with using commits? Sometimes ...
-----Ursprüngliche Nachricht-----
From: Christopher
Sent: Tuesday, April 28, 2020 2:34 AM
To: [email protected]
Cc: Jens Geyer ; Daniel Gruno ; Users
Subject: Re: Spammy gitbox
It doesn't look like Thrift has a separate notifications list. I
recommend requesting one, then updating the .asf.yaml file in the repo
to send notifications there.
On Mon, Apr 27, 2020 at 5:49 PM Daniel Gruno <[email protected]> wrote:
Please see https://s.apache.org/asfyaml-notify for how to set up
notifications yourselves. This is largely a corrective measure that's
happening for messages that were supposed to go to your list a long time
ago but never arrived. You can pick any list to send them to, including
commits@, issues@ or even set up a new github@ list for these messages.
On 27/04/2020 16.33, Jens Geyer wrote:
> Hi infra,
>
> we did not trigger any changes AFAIK. So how can we stop that from
> happening?
>
> We're getting complaints, and I tend to agree. It is slightly disturbing
> to have this "service" enabled without at least some bit of warning what
> is ahead. What "services" can we expect next to come over us?
>
> Suggestion: We already have a [email protected] mailing list,
> maybe that is the better candidate for this kind of automated
> information.
>
> Best regards,
> JensG
>
>
> -----Ursprüngliche Nachricht----- From: Christopher
> Sent: Monday, April 27, 2020 7:35 AM
> To: [email protected]
> Subject: Re: Spammy gitbox
>
> Ping. Please move GitHub email notifications to a separate list. They
> are making this dev list impossible to follow.
>
> On Thu, Apr 23, 2020 at 5:18 PM Christopher <[email protected]> wrote:
>>
>> Hi Thrift Devs,
>>
>> Recently, it seems GitBox has been updated to start spamming the
>> Thrift dev list. This produces a lot of redundant noise if somebody is
>> already watching the repo on GitHub. Can these be sent to a separate
>> notifications list for Thrift instead, so followers of the Thrift
>> mailing lists can more easily choose whether or not to receive these?
>>
>> Thanks,
>> Christopher
>
