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 1gjtA5-0005xd-84 for pgsql-www@arkaria.postgresql.org; Wed, 16 Jan 2019 21:55:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjt95-00031q-Fr for pgsql-www@arkaria.postgresql.org; Wed, 16 Jan 2019 21:54:47 +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 1gjt95-00030Q-7H for pgsql-www@lists.postgresql.org; Wed, 16 Jan 2019 21:54:47 +0000 Received: from mail-qk1-x741.google.com ([2607:f8b0:4864:20::741]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjt92-0003A4-7g for pgsql-www@postgresql.org; Wed, 16 Jan 2019 21:54:46 +0000 Received: by mail-qk1-x741.google.com with SMTP id y16so4782649qki.7 for ; Wed, 16 Jan 2019 13:54:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=8ovl2zZxVKltzE5DX3Qj4dLT3YM4lOp5frkaU59TPdU=; b=fmma5upDh9ZvNZjKnclnrK2CmUq6R6mHTxiRhQmA3qtih8bsZ6FYe6M5boCF5X0rFC VuGg6NthFSUNx1fcg+5NwTM4BmqaoDYyAq3wTjCxwt2fGU9pXbRM2x3G13LM4o1aRIoY y3go3f883IoW9+nL3AbnzBoKjeUfvl9iruLGqwH79MoU437ymaKmnKoWIt+azmE94uTL j2bUzMmgD9Sj+DIKS/rHnEt+IF+cxvGtGQ7QZU69sLWUdSI6aRpqmV02mYR1S8tvgZos +qcXCN1z+HGiicP3osJHTC1XVtn56YNh9xGofKYDmiqQ9qsxpssAlsxymF5QJ9eq/m7M z/pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=8ovl2zZxVKltzE5DX3Qj4dLT3YM4lOp5frkaU59TPdU=; b=myKA1NeA4MvBIg1HDuXQpxN20Q2OpnLRv+m+K5FUGc6MNyGQXu5i6w5F02f4+avvQ1 Udwz2iwno16pEMsdXEp5MF/zuC24iXE+CUezaXsV7EPV087pE+fT7txM58TihONSWdqB 7Anv7a/mTFNoP0Nh/TpG7yhh7LwxT328bD4uqHlC+HFYO7hhypL2V9qf1B1773Z8mJ38 B0yMyQvQcyHCQzluOGSC1QZ07HCo/v74RsLSpPXe3XWXwxkDLEesZLYW5NfA5LJK8CKT HiBw9PFbF1D51k27orLjOIKATp/cddaucFsu2YLZkmeqB9UGMnD1+H/Cwa1DzLtNCiUb vrHQ== X-Gm-Message-State: AJcUuke09lFzI98xxLdPpOolJrjKPuW9viQitjGCMPwDxNl0vihOJlaC vQVRX0D830m+rwXKnY8C3+3Glw== X-Google-Smtp-Source: ALg8bN5t1vCTb555v7OMtMmhpeai9BDZPJYqZNmrYHLeOpGWHrjGdLMVTsdghdittKT4pZCdnjfe8A== X-Received: by 2002:a37:6a84:: with SMTP id f126mr8519809qkc.342.1547675683380; Wed, 16 Jan 2019 13:54:43 -0800 (PST) Received: from alvin.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id r47sm53161819qtc.77.2019.01.16.13.54.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 16 Jan 2019 13:54:42 -0800 (PST) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 05A9574B; Wed, 16 Jan 2019 18:54:41 -0300 (-03) Date: Wed, 16 Jan 2019 18:54:40 -0300 From: Alvaro Herrera To: Stephen Frost Cc: Andres Freund , Magnus Hagander , "Jonathan S. Katz" , PostgreSQL WWW Subject: Re: mailing list redirect for bug numbers? Message-ID: <201901162154.tg6vsmfylacs@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190116195327.GF2528@tamriel.snowman.net> User-Agent: NeoMutt/20180716-1013-2c1e88 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Jan-16, Stephen Frost wrote: > 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. The issue is that people working offline want to be able to figure out emails in their local mailboxes looking just at the contents of a commit message. This is trivial if the URLs contain the message-id, and impossible if they don't. With bug numbers, the situation is the same: if, while offline, you have 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. Based on this, my opinion is that a redirection system that handles https://postgr.es/bug/8470 by redirecting to message https://postgr.es/m/E1VOpEt-0003nc-4J@wrigleys.postgresql.org works fine, because I can look up the thread by looking for the bug number in the subject. If we do anything more complicated than that (say a database filled with message-ids based on bug IDs that don't appear in the message subject), that workflow fails when I'm offline. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services