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 1gk5vZ-0006Ze-T1 for pgsql-www@arkaria.postgresql.org; Thu, 17 Jan 2019 11:33:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gk5vW-0007tw-SR for pgsql-www@arkaria.postgresql.org; Thu, 17 Jan 2019 11:33:38 +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 1gk5vW-0007mW-G4 for pgsql-www@lists.postgresql.org; Thu, 17 Jan 2019 11:33:38 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gk5vS-0004yD-KF for pgsql-www@postgresql.org; Thu, 17 Jan 2019 11:33:37 +0000 Received: by mail-lf1-x142.google.com with SMTP id v5so7500691lfe.7 for ; Thu, 17 Jan 2019 03:33:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IUY3II9PA0VnK1a1lZTH2FQWthX75pingV2oT+gh+i4=; b=gXHOee+JmscWAZthC/hAmXr32RgRCL58Py3BuaD+iAJ7Ea/ZPcwU3a1oNsHUW5RG2P i+mGebjQ1hcaS++gYC2PKU8PebajMgtOiJdDucAYSxHAH0xHH6XU5FvX0U5sqLZSI5XY Lyf57/0RHhaeaSeNmXbR5s72bBjR3WJ6bP0hQRhZdhyR0ntEmh7k6heBznKD4UeksQCx Y8mBDewiploEsRuu72ZYD6ESXGoHRv4j8QQU7f3SDBTmFe7y9gfdPaCi73X5GSxpgLnR Wtct3/BNOH9O+0h4Bg1oXlDJVhEZGsMB6cV1vopHgbyccXQ5VE+nT2BOsRju2pBGiqcc Q6Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IUY3II9PA0VnK1a1lZTH2FQWthX75pingV2oT+gh+i4=; b=DrkqEAO+3Vtxf7rDQZ3psVridxVyGI7bGhuHCO9qi7bKQFOWFsWDIVW1zDnNqvwv4G EiYijnHQTfAHanQynrINDBSfnVciyF3yUEgmJbT6B1uaqAvlwjWgKXpSdHwkqz2Qe1ts 96cqf+ku5tb2hR9yyW7Fj9OTMul6sIs6xy4BHMfw/Vb2Wpd83wjvaDM0TmrvKYB0Jzrl H5DNkoOfqfLNT1jTrtDbAyNAki9BQuwPenKTtY2L93g9aGYMKguYq1aO8TWiWiGCBeWc ivdeePT2QsTZD2biCfEumndb8zE3QCZde2gZOyVVkehAH9HbI8TUFonNkPpMgWKesrr4 tLkg== X-Gm-Message-State: AJcUuke6yCY8OoidMljbb9SwaJdvUyolDITyMMuvwdtrAKnsMCLBcrNJ Vw6ACsyM0NMfNmtrbZF3cLNaDXRlsxxNk1CXnUVRnA== X-Google-Smtp-Source: ALg8bN4tUAboDUVxF5ZjzGaBziY3Xf02LSksG8wJQInK6wLxIhTDuBJD79EF3oYNl5sckdjhWdO3zOoAvukZs7jlxD4= X-Received: by 2002:a19:6514:: with SMTP id z20mr9623613lfb.31.1547724813575; Thu, 17 Jan 2019 03:33:33 -0800 (PST) MIME-Version: 1.0 References: <201901162154.tg6vsmfylacs@alvherre.pgsql> In-Reply-To: From: Magnus Hagander Date: Thu, 17 Jan 2019 12:33:22 +0100 Message-ID: Subject: Re: mailing list redirect for bug numbers? To: Dimitri Fontaine Cc: Alvaro Herrera , Stephen Frost , Andres Freund , "Jonathan S. Katz" , PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000b9436a057fa5c3d8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000b9436a057fa5c3d8 Content-Type: text/plain; charset="UTF-8" On Thu, Jan 17, 2019 at 12:09 PM Dimitri Fontaine wrote: > Alvaro Herrera writes: > > 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. > > Is it possible to add custom email headers in the pglister system, > something like maybe X-PostgreSQL-Bug, so that the bug ID number is > clearly assigned to emails? > > Such a system might also be backwards compatible when backfilling bug > numbers to threads that don't have them yet. Local archives will need to > be synced again of course, but then it's easy to grep for the > X-PostgreSQL-Bug and find the email thread again, right? > > Doing that in pglister seems like a terrible idea. But if we want to, we could do it in the actual bug generation form, sure. That would be trivial. But we can't do that backdated on existing mails. In the archives they're immutable. So they'd be for new emails only. So I'm not sure it would actually help very much? //Magnus --000000000000b9436a057fa5c3d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jan 17, 2019 at 12:09 PM Dimitri = Fontaine <dim@tapoueh.org> wro= te:
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> With bug numbers, the situation is the same: if, while offline, you ha= ve
> 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.= =C2=A0 If
> you have to contact a web interface to figure out what the thread is,<= br> > that workflow fails.

Is it possible to add custom email headers in the pglister system,
something like maybe X-PostgreSQL-Bug, so that the bug ID number is
clearly assigned to emails?

Such a system might also be backwards compatible when backfilling bug
numbers to threads that don't have them yet. Local archives will need t= o
be synced again of course, but then it's easy to grep for the
X-PostgreSQL-Bug and find the email thread again, right?


Doing that in pglister seems like a terrible idea. Bu= t if we want to, we could do it in the actual bug generation form, sure. Th= at would be trivial.

But we can't do that back= dated on existing mails. In the archives they're immutable. So they'= ;d be for new emails only. So I'm not sure it would actually help very = much?

//Magnus

--000000000000b9436a057fa5c3d8--