Date: Sat, 19 Jan 2019 10:11:46 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>,
	Dimitri Fontaine <dim@tapoueh.org>,
	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: <20190119151146.GS2528@tamriel.snowman.net>
References: <20190118154019.GP2528@tamriel.snowman.net>
 <201901181617.movyyirllj2h@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="i0LkSOiDkWwM5/LT"
Content-Disposition: inline
In-Reply-To: <201901181617.movyyirllj2h@alvherre.pgsql>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk


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

Greetings,

* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> On 2019-Jan-18, Stephen Frost wrote:
>=20
> > > since copies received via a direct cc: rather than via the list would
> > > lack the field.  (Hence, you're mistaken to claim this would be
> > > locally searchable.)
> >=20
> > Ok, it's only locally searchable for people who are subscribed to our
> > mailing lists and keep local copies of the emails they get from our list
> > server, but isn't that going to cover the vast majority of the people
> > who are going to be looking in the commit log and trying to find a
> > matching thread in their local archive..?
>=20
> It doesn't work in that case either if you're CCed and you get the
> direct copy before the list copy; that one won't have the header.
> In my case I just deduplicate with formail/reformail and it simply
> throws the second one away, and I suspect others do likewise.  I don't
> know what does Gmail do.

I used to do that too but then you may also miss headers from pglister
which direct where the email gets saved, at least for me, so I've gone
away from using a local de-dup system like that based on message ID
(independently, I have also seen idiot mail senders duplicate message
IDs for different messages, which has also made my shy of having
something that just throws away email based on that...).

> > If we just agree to always use the message-ID of the first message in
> > the thread when we're closing out a bug, and people are happy with using
> > message-ID, then I'm not really sure what the bug # is doing for us (and
> > I see that that question from my prior email wasn't answered).
>=20
> Hmm, sometimes I refer to an intermediate message in a thread, not
> necessarily the first, when something was discovered in the middle of
> some discussion.

That certainly is a perfectly acceptable option, imv, though I suppose
it does complicate things a bit since then you do have the multiple
message IDs question, but if what you really want to link to is
something down in a thread, even if it's a thread with a bug ID, I would
say that the issue is still there even if we add a way to link to bugs
by ID.

I suppose, in the end, committers will still need to be thinking about
what they put in the commit messages regarding links, but then, that's
also not necessairly a bad thing.

Thanks!

Stephen

--i0LkSOiDkWwM5/LT
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIcBAEBCgAGBQJcQz4yAAoJEO1sijiDR2RV1RsQAMMMBsKyIEZV/ssODG/MGJmL
iLwCCauk1QTGqwt/sQPy3z6VjPszBFXpX+Ine6JwGsPhjL3tAnLNLCLoV1wjWHn9
Uk/uWAhaPM6wDWJG2Em7GoyPwAuDuNQrtrEtMjoV58FFS0YGAFkHNRHRZUtXAI3c
sklicM0e4DpHzh+r4eUd3ykR8YdZ8X+KC7ufw7tOW6GADu0/QAlJ+kYHS6UbbnGh
jW4JE7bEwRwjNCeGr6dZxotHzxVtJU3X2Tga0MGVOOvcDKI3S23yC6FyTL55u+CD
t4MAkMJH3NLoZvJ0VJ8Bet0k4GJcqKQnPpMEXpmYcJBpUTpCdU3qr2hXBtpQguL1
IW3RM9CcxVZU/lh4WEyKNSyv0ZMtMdKQB95x+yFvdPBvd8VpMyh7HQo9YkkUVuGj
Al2ay/0hPpNbmaUQ3hI6T30J9fPhU3GXPkt49qcC1ho1Q0LQ2b8NZy0S7hGVFU2o
q2o4N2Rd4A6Dun0zvfjlTIYck5K6Tlutxsr3ohgZL4Awjvj7C9GJzaYnh2/T+/zY
Yjilvulhtu/n+aUO6IzIbS8lSyUEW5VWXPE9005iHEoOb7jHjCRcHQZ2mN6cE3NQ
ToWvsUsb3JP/wN6kTklVPUSPg8cP2TkyWEyiZAfQGR9vXbF7o8xTz1dT7EcbBGXP
53cBK+naZPwJjuwUjRFD
=qRxF
-----END PGP SIGNATURE-----

--i0LkSOiDkWwM5/LT--