public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Stephen Frost <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Dimitri Fontaine <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: mailing list redirect for bug numbers?
Date: Wed, 6 Feb 2019 13:41:06 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2019-Jan-19, Stephen Frost wrote:

> I didn't come to the conclusion that we just should leave everything
> as-is.  I was hoping to either get to a point where either we come up
> with a sensible way to provide a bug number or other identifier for
> things we typically want to link to from commits, or decide that the bug
> number isn't really all that useful and get rid of it.

Well, we already have bug numbers in bugs submitted via the website and
they seem to work pretty well.

What if we add an email interface that creates bugs with IDs, but
nothing more than that?  I'm thinking a special address such as
[email protected] that creates the bug ID and resends to
[email protected] CCing the bug reporter, after changing Subject
to include the bug ID and the From/Sender to an address under our
control (to avoid DKIM problems with the reporter's domain).  It would
work normally using pgsql-bugs from that point on.

If we have our system preserve References/In-Reply-To headers, I think
it would even work to add a CC the special address in the middle of a
regular thread in a mailing list (any mailing list, not just pgsql-bugs)
to spawn a new bug.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

view thread (32+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: mailing list redirect for bug numbers?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox