From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
cc: Magnus Hagander <magnus@hagander.net>, Dimitri Fontaine <dim@tapoueh.org>,
        Alvaro Herrera <alvherre@2ndquadrant.com>,
        Andres Freund <andres@anarazel.de>,
        "Jonathan S. Katz" <jkatz@postgresql.org>,
        PostgreSQL WWW <pgsql-www@postgresql.org>
Subject: Re: mailing list redirect for bug numbers?
In-reply-to: <20190118143505.GN2528@tamriel.snowman.net>
References: <201901162154.tg6vsmfylacs@alvherre.pgsql>
 <m2sgxr8rsg.fsf@laptop.tapoueh.org>
 <CABUevEy9UHfER0-f+=KJ80ChY525jBfyv9YVdrjvd925tvNmcQ@mail.gmail.com>
 <20190117154202.GH2528@tamriel.snowman.net>
 <CABUevEyHXGJU9aezrXSKp+JN=ckSQpWmpZk7TOBnfiCt6MGG1Q@mail.gmail.com>
 <20190117182821.GK2528@tamriel.snowman.net>
 <CABUevExPzZ_weWh6F+Uhqa3jxttYx1RmHUyx5zB44h=bj7jqsw@mail.gmail.com>
 <22663.1547759616@sss.pgh.pa.us> <20190118143505.GN2528@tamriel.snowman.net>
Comments: In-reply-to Stephen Frost <sfrost@snowman.net>
	message dated "Fri, 18 Jan 2019 09:35:05 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24595.1547824622.1@sss.pgh.pa.us>
Date: Fri, 18 Jan 2019 10:17:02 -0500
Message-ID: <24596.1547824622@sss.pgh.pa.us>
Precedence: bulk

Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> Agreed.  If we have bug numbers assigned to messages that aren't bugs,
>> or are replies to bugs, it's just going to be a mess.

> In my suggestion, replies to bugs that are sent by a sensible MUA would
> have the bug # of the bug being replied to-

Uh, how?  Assuming that "your suggestion" refers to the 'X-Pg-BugId'
idea, I think the chances of that being included in replies are nil.

> In other words, we'd add a header like:
>    X-PG-MessageId: 123453
> And then be able to use links like:
> https://postgr.es/p/pgsql-hackers/123453

Seems like this is reinventing message-ids, and not very well either,
since copies received via a direct cc: rather than via the list would
lack the field.  (Hence, you're mistaken to claim this would be
locally searchable.)

> Just to wrap this up, what I'm trying to get at is that I'd rather we
> try to solve for the specific issue that came up rather than building a
> solution on something that's already only a partial answer to begin
> with, in that we often want to link from the commits to discussions on
> -hackers or to emails to -bugs that didn't have a bug # and those aren't
> addressed with this particular approach.

The existing solution is "use the message-id", and that seems to work
well enough.  Yes, gmail's message-ids are annoyingly long, but that
seems like only a cosmetic objection.  I'm not seeing anything here that
really looks like it'd be an improvement.

			regards, tom lane