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 1gjrOs-0000i8-Pm for pgsql-www@arkaria.postgresql.org; Wed, 16 Jan 2019 20:02:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjrFk-0005VV-6G for pgsql-www@arkaria.postgresql.org; Wed, 16 Jan 2019 19:53:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjrFk-0005T5-0y for pgsql-www@lists.postgresql.org; Wed, 16 Jan 2019 19:53:32 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjrFh-0000uz-TY; Wed, 16 Jan 2019 19:53:31 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id AF0A85F79E; Wed, 16 Jan 2019 14:53:27 -0500 (EST) Date: Wed, 16 Jan 2019 14:53:27 -0500 From: Stephen Frost To: Andres Freund Cc: Magnus Hagander , "Jonathan S. Katz" , PostgreSQL WWW Subject: Re: mailing list redirect for bug numbers? Message-ID: <20190116195327.GF2528@tamriel.snowman.net> References: <20190114221809.eymqah36d6uq5nir@alap3.anarazel.de> <9cfc2880-0623-7cc3-45f4-342c3af881fe@postgresql.org> <20190115191915.eavj4i4mmf5wmoaf@alap3.anarazel.de> <20190116183855.GD2528@tamriel.snowman.net> <20190116192831.tweascbph7eappwe@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pbhtfbmonhYEtFF4" Content-Disposition: inline In-Reply-To: <20190116192831.tweascbph7eappwe@alap3.anarazel.de> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --pbhtfbmonhYEtFF4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Andres Freund (andres@anarazel.de) wrote: > On 2019-01-16 13:38:55 -0500, Stephen Frost wrote: > > * Andres Freund (andres@anarazel.de) wrote: > > > On 2019-01-15 11:57:21 +0100, Magnus Hagander wrote: > > > > On Tue, Jan 15, 2019 at 11:43 AM Jonathan S. Katz > > > > > The only big catch I see is that if someone emails -bugs directly= , no > > > > > number is assigned, so we would have to leave that be. > > > >=20 > > > > Yeah, those would be entirely out of scope. > > >=20 > > > Agreed. I previously wished there were an email based interface to > > > submitting a bug, but that'd just be that, a new interface for > > > submitting a bug. > >=20 > > This got me wondering... why? >=20 > Why I want it, or why I think it's out of scope? "Why does it need to be a new interface?" is what I was going for there. > > This discussion is all about building a mapping between a Bug# and a > > message-ID. If we do that, why not fill it in completely? As in, have > > a Bug# for every thread on -bugs, either the one assigned by the webpage > > or one which we assign when we see the email come in and then backfill > > that? >=20 > Well, one problem is that we can't offer the same subject based UI, at > least not trivially. We'd have to rewrite emails that aren't replies > to an existing thread to come from a different sender to have a > different subject and not fall afoul of dkim et al. No, we can't rewrite the subject, and I wasn't suggesting that we do so. > It seems pretty reasonable to do that, but not a small task, so I just > don't think it should be bundled with the, I think, smaller task of > just building the mapping. Doesn't seem like there'd be a lot of > wasted effort by doing these separately. I'm not against doing them independently, but I don't think the level of effort required to simply fill in a bug number for any message-id we find that doesn't match the subject-based search we'll be doing for the bug # would be very much. The bigger question that I'm trying to ask here is for input on how useful it'd end up being or if people don't think they'd actually use it. As I recall, we actively discussed doing something similar for -hackers, to shorten up the URLs going into commit messages but there was some concern over having a mapping from IDs to message-IDs. I'd have to go dig up the thread to remember what the issue was there. Thanks! Stephen --pbhtfbmonhYEtFF4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJcP4u3AAoJEO1sijiDR2RV1WsP+wTOKjZ4iGTao+HhWnY7xr/c IxAg4pGqpCaRV3+Td0vbXi9Bf1s94CcOfLc7SeJMRMw5tSzo38zVAXFHlW8uJAvS RMI77CVxOLT5tPzXGcnjXnzYPmikZWnIaL70TFSWrcbTLqJTONt+pFqFhrPe9lYa gdR4n4UXe15Elz+IxDypLYuGU4lvaJriZJyxJgL+OAxD9SkLY+KpuRgor6rpe0AW IrQUGIcoo+DaEBS88P2QNifrEdM122YjsHbBflEVzCmUf6zW5Eq787HoDCQJmKDi q1rnSHvuqBMaIlfTsyejE3GO4wahcePbg3Blod7nEurk72c61Vm9xFNEd19taaWi iUbNT5046SZZvs+CzSI6yFmMEm5xDTLHe+rlnUY2GsXeIDaL7Ad5Si3MR9/4XRVi HI7fSWMADejF/0wXP3B0NkrCZHFwuO9xGnExIpOvRKpWKf2/+42JT+ng5HkEKZJA F0tVGiRxcYjsqsIC5bYBkHOYyNWmaM29Fbzf1T2unt97XeenQIKnyXwWCoCk/4iy q8imFXEJxQtaWT6RLqSMqMd3J4UHkArUSF+GZkXkAUVe7n5TuaK3QGzqGPTiUCpp ivrF774XBhMr9R8r253+mlHsCA1zTHWRN2gn05f1Rp2F0q2ZLlAT1hmaeWZnWFY3 +p4UIwerD+Mz9VrPq/76 =Yii8 -----END PGP SIGNATURE----- --pbhtfbmonhYEtFF4--