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 1gjqvM-0002f4-22 for pgsql-www@arkaria.postgresql.org; Wed, 16 Jan 2019 19:32:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjquL-0000Oh-JN for pgsql-www@arkaria.postgresql.org; Wed, 16 Jan 2019 19:31:25 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjquI-0000MQ-Kl for pgsql-www@lists.postgresql.org; Wed, 16 Jan 2019 19:31:25 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjqrc-000586-E7; Wed, 16 Jan 2019 19:28:38 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 3A7A828383; Wed, 16 Jan 2019 14:28:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 16 Jan 2019 14:28:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=bYON/RXysa1uwKd+TGP5kfV8o7+ NjscH4lOA9iAEG7Q=; b=csDFJAgw7LyFX2tX6eyHDQ6PM1WhOgMDksaLJmMGvx6 ZiU5zITronqzoXw/MtQSmvXtK/U4SO/mkk3aaRlfboqlu5wK5UzJEHe3SjtaKXXH gsxUTLadb7gPZY33NZxp5hBs82PAT3SfpP0bSNkZAGNK8EFhQ+TbZ61SZpJa6nhJ GkStFHFcZ6OgMFi5WCkQDbhJb17E/hn3Vz2V1YdbHHfELmYdf393GDPHoi0ZIUfR zho5Zezx2ikqLfkueqif6cbCuPMX948BwTghB6DwK+TswD4K3vk4AxglhQRU7VY6 FzBStUOUnSHobOXUmWJNIR+Z/BjHhwlpBuoGG4VnOVQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=bYON/R Xysa1uwKd+TGP5kfV8o7+NjscH4lOA9iAEG7Q=; b=MbnIzXxdGiTc2pWmqgTTza fHP1jQQ6vAP+cnKlIsQuEBYkF1Dk6tabDpLHgjpKx+6gdEyOAKyHnzu7AG/PM9cR F2vM+u1vQzyzuGoXB0NKNMj9gv+CWEybQGXPufUSh1mnoDH56xAfIkTmoa9EoSif J2P0k4rd6BQNxNcLBgS2pE8V1sABhSUWcntoawq/iXDSVGTkabTfeM4m3riGmrfm PbPAKNRA6FYZRzkQhsyAVaPmZ6a+rBMbV4mAkfNuN1zXNv27A+GE2AfT5Jr4Gk6A jNaDK2F++mohfov5YrVaYobfld0UTJgozxYNd2+4+OMIfAeyp7Be/SkQfOi2u0iA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgeehgdduvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfh ggtggujgesthdtredttddtvdenucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegr nhgurhgvshesrghnrghrrgiivghlrdguvgeqnecukfhppeelkedrvddutddrudegtddrud ejudenucfrrghrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdr uggvnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 13BCE100BA; Wed, 16 Jan 2019 14:28:32 -0500 (EST) Date: Wed, 16 Jan 2019 11:28:31 -0800 From: Andres Freund To: Stephen Frost Cc: Magnus Hagander , "Jonathan S. Katz" , PostgreSQL WWW Subject: Re: mailing list redirect for bug numbers? Message-ID: <20190116192831.tweascbph7eappwe@alap3.anarazel.de> References: <20190114221809.eymqah36d6uq5nir@alap3.anarazel.de> <9cfc2880-0623-7cc3-45f4-342c3af881fe@postgresql.org> <20190115191915.eavj4i4mmf5wmoaf@alap3.anarazel.de> <20190116183855.GD2528@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190116183855.GD2528@tamriel.snowman.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, 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. > > > > > > Yeah, those would be entirely out of scope. > > > > 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. > > This got me wondering... why? Why I want it, or why I think it's out of scope? > 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? 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. 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. Greetings, Andres Freund