Date: Thu, 17 Jan 2019 10:42:02 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Magnus Hagander <magnus@hagander.net>
Cc: Dimitri Fontaine <dim@tapoueh.org>,
	Alvaro Herrera <alvherre@2ndquadrant.com>,
	Andres Freund <andres@anarazel.de>,
	"Jonathan S. Katz" <jkatz@postgresql.org>,
	PostgreSQL WWW <pgsql-www@postgresql.org>
Subject: Re: mailing list redirect for bug numbers?
Message-ID: <20190117154202.GH2528@tamriel.snowman.net>
References: <201901162154.tg6vsmfylacs@alvherre.pgsql>
 <m2sgxr8rsg.fsf@laptop.tapoueh.org>
 <CABUevEy9UHfER0-f+=KJ80ChY525jBfyv9YVdrjvd925tvNmcQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="4s4JkUeKfZa1A9vU"
Content-Disposition: inline
In-Reply-To: 
 <CABUevEy9UHfER0-f+=KJ80ChY525jBfyv9YVdrjvd925tvNmcQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk


--4s4JkUeKfZa1A9vU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

* Magnus Hagander (magnus@hagander.net) wrote:
> On Thu, Jan 17, 2019 at 12:09 PM Dimitri Fontaine <dim@tapoueh.org> wrote:
>=20
> > Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > > With bug numbers, the situation is the same: if, while offline, you h=
ave
> > > 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?

This was exactly what I was thinking too, to avoid the issue with the
Subject field.

> > 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 trivia=
l.

Doing it in the bug generation form would only be half a solution
though.  Beyond the concern about pglister being too 'PG' specific,
what's the issue with having it able to add such headers..?

> 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?

We could certainly provide the mapping for old emails even if we don't
want to actually change the existing emails (although I'm not entirely
convinced it'd be such a bad idea to include the bug numbers somehow..),
and, really, we're talking about commits going forward, so is the issue
that old emails don't have it actually a problem?  New emails would and
the commit log moving forward is much more likely to reference new bugs
than old..

Thanks!

Stephen

--4s4JkUeKfZa1A9vU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJcQKJJAAoJEO1sijiDR2RVAtQP/i2/cfq3C8CZRdGMBAbtTWcm
SXSlt42nMtF0kpIbYrj4o981g8cAI5Hoipa/VyMAAQ3N0mJ4eKZEl9bu4bOjDEKS
2VttjNSecB+Zvs2rQAGPM52IVNIhSJlZApEiYkeABCCyRYRPrEiErP/cMAj45e4q
NV0d4QzjjxUaahnSyc+9KTu1HDSU7qp2gVEwzI+px4MH4IcoFr3Z54GwqmG8GM0e
5jpxbFeNPdm+87lgVaTZbVaRPKgRv70K6cDzYN+EfycpNtbmpMc7GPv/Tob5sLg9
uT6MTPCig2u421c9h3D4Y5OzTvKPF7jpKDpHFgsW0m/OGUUuKi+E8k1Ja4vdF3SW
jCNQI29b/WKSWEVuoh8tHK2amP4jFlorWTX7uUbSkpCM67aQ/eDLUiN0Cx9pNOuV
u06+18MfQb5TmjZsmzxezbLGD0k//vFpxwYxzwtDrGKrrYdkyaCiiLv6qNnOCcx6
fDJ6SQeW5FV7KRNI7YQtKZoCSZC/zQQFi2IEkU5ej4s7+rJ0FAfgX3hm+sZ90GOG
P0b25MbPWsCI07K2WoWwrM29ZPmpUCuzhXxzwBDkuSI63jCEeWhsPExLGO28YUjP
50gyZdSmeCb2+fnycgdgjC51zrQz//HL71FC1n8Oqusu9UTsE7hkyjAn5c2MVybs
yD4Kvq1S1kEnUTkmlBuV
=/+eE
-----END PGP SIGNATURE-----

--4s4JkUeKfZa1A9vU--