From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Commit emails to -committers |
Date: | 2021-08-20 13:56:44 |
Message-ID: | 1852845.1629467804@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> For that reason I'd lean towards having something just be "PostgreSQL
> commits <noreply(at)postgresql(dot)org>" and not put the name in there at all
> -- the name would of course go in the body.
That'd be OK with me.
> Another option we could go with would be to have the email sender be
> "Stephen Frost <sfrost(at)postgresql(dot)org>", since we have by policy been
> giving all committers such an email address. We'd need to add the
> ability to do that mapping into the commit message script as it
> doesn't have it right now, but it would be doable. And of course, it
> would suddenly make it more important for committers to ensure that
> this forwarder or mailbox actually works.
FWIW, I've been bit-bucketing mail via tgl(at)postgresql(dot)org for many
years, because it's all spam and I don't have any ability to filter
it based on the true source. I don't really want to have to start
treating that as a valid address.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-08-20 18:20:58 | Re: Commit emails to -committers |
Previous Message | Magnus Hagander | 2021-08-20 13:35:10 | Re: Commit emails to -committers |