Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gks17-00059E-H5 for pgsql-www@arkaria.postgresql.org; Sat, 19 Jan 2019 14:54:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gks15-000633-MX for pgsql-www@arkaria.postgresql.org; Sat, 19 Jan 2019 14:54:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gks15-00062w-DK for pgsql-www@lists.postgresql.org; Sat, 19 Jan 2019 14:54:35 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gks12-0005cu-TK; Sat, 19 Jan 2019 14:54:34 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 612385F79E; Sat, 19 Jan 2019 09:54:32 -0500 (EST) Date: Sat, 19 Jan 2019 09:54:32 -0500 From: Stephen Frost To: Magnus Hagander Cc: Tom Lane , Dimitri Fontaine , Alvaro Herrera , Andres Freund , "Jonathan S. Katz" , PostgreSQL WWW Subject: Re: mailing list redirect for bug numbers? Message-ID: <20190119145432.GR2528@tamriel.snowman.net> References: <20190117154202.GH2528@tamriel.snowman.net> <20190117182821.GK2528@tamriel.snowman.net> <22663.1547759616@sss.pgh.pa.us> <20190118143505.GN2528@tamriel.snowman.net> <24596.1547824622@sss.pgh.pa.us> <20190118154019.GP2528@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Nk/5ojoyUvI/LTs/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Nk/5ojoyUvI/LTs/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Magnus Hagander (magnus@hagander.net) wrote: > On Fri, Jan 18, 2019 at 4:40 PM Stephen Frost wrote: > > If we want something that would work with replies for direct CC, then > > we'd have to (ab)use a field that we know MUAs will copy to the next > > email on a reply and there's unfortunately few of those. At least > > some bug trackers have dedicated email addresses for individual bugs, > > probably for that reason, among others. >=20 > Technically we already have this for threads started in the form these > days, as you can trivially get the bug number out of the message-id, and > the message-id is one of the fields that *is* typically preserved (in the > References header). Hmmm, we certainly can't change the message-ID in-transit, but I wonder about the References field and/or In-Reply-To... > It won't cover threads that are responded to by creating a whole new thre= ad > and referencing the bug in the free text part of it, but there's really no > way to handle that form inside the email... Yeah, which also means it's difficult for someone who isn't on the list and not on the original email to add to a bug... That might be solved if/when we implement the "email me this message" feature that we've discussed a few times. Thanks! Stephen --Nk/5ojoyUvI/LTs/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJcQzooAAoJEO1sijiDR2RVS8wQALjhHK5M4BOwPkhvA3O59L09 cYPLnwo8udfP8++EXWxepK4iuNZXn7zDz223aqhT7NH7C5V/C6MMnY1XN14a8LXi XUy3G7UQKfOQ1LOy1GHnfsDr6uDQYSvNcXByXiBFm1CnHyRTEgN7N/r7yRNEK9Nq KQOolEH2NZlL3PL6G3vppWugmn6tm06mh8KjldXA8hxfsbXtqqKqgZYs/QRnQn0R bR2Wjph2f9btpVJpOwAyq9zUmjrZm6h6zpsLUL9Wug/BalqFQQnXS3U/XItj/cmg 2P6DY4TgB93ddjNoSgNCExWFsniXG4S+KatbRV/stEmNihdNJ4gxpuyQwf+xIgM4 jNd7+vqJhoieFKqsO+uOEdVbSLgl7X12eKgMI5e4LT9q5sjDuofzNtRRb/cO+Bn2 ZQCK0SL/N+jbLZs4h2ZUOo7rxLX1TLRu6KMWJuNuJabhIhI2RZnVOJJtEJmAYedl uMdv8qH0w6/qnMpGVjAjlMDSvFQA7GjgF4vhEScMUTROmJuSjxMuUbsEwCc1szm+ ogLncT9E0qFwsWlsTM09XcnGllXDXGm5lbUEhcg15qzPA/5FL5rx0uCp8lHJZOaR moHrmTNcC2u+YR7PgKRk3VdoYYQSPTbnVHHZxdlJbytIfXELS2Tpal7M2gEgbvFc h01BKTmLyZZvVcVYQ0tJ =iyIP -----END PGP SIGNATURE----- --Nk/5ojoyUvI/LTs/--