[arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

Sébastien Luttringer seblu at seblu.net
Tue Jan 3 02:33:24 UTC 2017

On Mon, 2017-01-02 at 15:50 +0000, Giancarlo Razzolini wrote:
> Hi All,
>    With the recent archweb migration, some services stopped working.
>    We are just finishing migrating those services (and automating them
>    on ansible). One of these services is the signoff reports emails.
>    For the past few days, the exact same e-mail was sent, from the old
>    setup, and nobody seem to have noticed. I guess most (all) filter
>    these emails out. Also, the service to populate the signoff's wasn't
>    running too, but this one will be kept running.
>    Also, I have been pointed to this[0]. So, should we send signoff
>    reports somewhere else or, not at all?
> Cheers,
> Giancarlo Razzolini
Please drop them.


Sébastien "Seblu" Luttringer
https://seblu.net | Twitter: @seblu42
GPG: 0x2072D77A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 821 bytes
Desc: This is a digitally signed message part
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20170103/75572749/attachment-0001.asc>

More information about the arch-dev-public mailing list