public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Dimitri Fontaine <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Stephen Frost <[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: Thu, 17 Jan 2019 12:33:22 +0100
Message-ID: <CABUevEy9UHfER0-f+=KJ80ChY525jBfyv9YVdrjvd925tvNmcQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Thu, Jan 17, 2019 at 12:09 PM Dimitri Fontaine <[email protected]> wrote:

> Alvaro Herrera <[email protected]> writes:
> > With bug numbers, the situation is the same: if, while offline, you have
> > a commit message carrying a bug number, and an offline mailbox where
> > pgsql-bugs threads are tagged with the same bug numbers, it's easy to
> > look up the thread based only on the contents of the commit message.  If
> > you have to contact a web interface to figure out what the thread is,
> > that workflow fails.
>
> Is it possible to add custom email headers in the pglister system,
> something like maybe X-PostgreSQL-Bug, so that the bug ID number is
> clearly assigned to emails?
>
> Such a system might also be backwards compatible when backfilling bug
> numbers to threads that don't have them yet. Local archives will need to
> be synced again of course, but then it's easy to grep for the
> X-PostgreSQL-Bug and find the email thread again, right?
>
>
Doing that in pglister seems like a terrible idea. But if we want to, we
could do it in the actual bug generation form, sure. That would be trivial.

But we can't do that backdated on existing mails. In the archives they're
immutable. So they'd be for new emails only. So I'm not sure it would
actually help very much?

//Magnus

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]
  Subject: Re: mailing list redirect for bug numbers?
  In-Reply-To: <CABUevEy9UHfER0-f+=KJ80ChY525jBfyv9YVdrjvd925tvNmcQ@mail.gmail.com>

* 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