| From: | Dimitri Fontaine <dim(at)tapoueh(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: mailing list redirect for bug numbers? |
| Date: | 2019-01-17 11:09:03 |
| Message-ID: | m2sgxr8rsg.fsf@laptop.tapoueh.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> 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?
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-01-17 11:33:22 | Re: mailing list redirect for bug numbers? |
| Previous Message | Magnus Hagander | 2019-01-17 09:33:49 | Re: mailing list redirect for bug numbers? |