MIME-Version: 1.0
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>
 <24596.1547824622@sss.pgh.pa.us> <20190118154019.GP2528@tamriel.snowman.net>
In-Reply-To: <20190118154019.GP2528@tamriel.snowman.net>
From: Magnus Hagander <magnus@hagander.net>
Date: Fri, 18 Jan 2019 16:43:42 +0100
Message-ID: 
 <CABUevEyeZajgv528df+iXtHm5WRYiSNe62=+RRiv4_kkuoAZ9g@mail.gmail.com>
Subject: Re: mailing list redirect for bug numbers?
To: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, 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>
Content-Type: multipart/alternative; boundary="000000000000d83930057fbd6077"
Precedence: bulk

--000000000000d83930057fbd6077
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 18, 2019 at 4:40 PM Stephen Frost <sfrost@snowman.net> wrote:

> Greetings,
>
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
> > 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.
>
> As I said, it would be done in the same way that our archives already
> figure out threading and pglister could then add it.
>
> If we want something that would work with replies for direct CC, then
> we'd have to (ab)use a field that we know MUAs will copy to the next
> email on a reply and there's unfortunately few of those.  At least
> some bug trackers have dedicated email addresses for individual bugs,
> probably for that reason, among others.


Technically we already have this for threads started in the form these
days, as you can trivially get the bug number out of the message-id, and
the message-id is one of the fields that *is* typically preserved (in the
References header).

It won't cover threads that are responded to by creating a whole new thread
and referencing the bug in the free text part of it, but there's really no
way to handle that form inside the email...

//Magnus

--000000000000d83930057fbd6077
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 18, 2019 at 4:40 PM Stephen F=
rost &lt;<a href=3D"mailto:sfrost@snowman.net">sfrost@snowman.net</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">Greetings,<br>
<br>
* Tom Lane (<a href=3D"mailto:tgl@sss.pgh.pa.us" target=3D"_blank">tgl@sss.=
pgh.pa.us</a>) wrote:<br>
&gt; Stephen Frost &lt;<a href=3D"mailto:sfrost@snowman.net" target=3D"_bla=
nk">sfrost@snowman.net</a>&gt; writes:<br>
&gt; &gt; * Tom Lane (<a href=3D"mailto:tgl@sss.pgh.pa.us" target=3D"_blank=
">tgl@sss.pgh.pa.us</a>) wrote:<br>
&gt; &gt;&gt; Agreed.=C2=A0 If we have bug numbers assigned to messages tha=
t aren&#39;t bugs,<br>
&gt; &gt;&gt; or are replies to bugs, it&#39;s just going to be a mess.<br>
&gt; <br>
&gt; &gt; In my suggestion, replies to bugs that are sent by a sensible MUA=
 would<br>
&gt; &gt; have the bug # of the bug being replied to-<br>
&gt; <br>
&gt; Uh, how?=C2=A0 Assuming that &quot;your suggestion&quot; refers to the=
 &#39;X-Pg-BugId&#39;<br>
&gt; idea, I think the chances of that being included in replies are nil.<b=
r>
<br>
As I said, it would be done in the same way that our archives already<br>
figure out threading and pglister could then add it.<br>
<br>
If we want something that would work with replies for direct CC, then<br>
we&#39;d have to (ab)use a field that we know MUAs will copy to the next<br=
>
email on a reply and there&#39;s unfortunately few of those.=C2=A0 At least=
<br>
some bug trackers have dedicated email addresses for individual bugs,<br>
probably for that reason, among others.</blockquote><div><br>Technically we=
 already have this for threads started in the form these days, as you can t=
rivially get the bug number out of the message-id, and the message-id is on=
e of the fields that *is* typically preserved (in the References header).</=
div><div><br></div><div>It won&#39;t cover threads that are responded to by=
 creating a whole new thread and referencing the bug in the free text part =
of it, but there&#39;s really no way to handle that form inside the email..=
.</div><div><br></div><div>//Magnus</div><div><br></div></div><div dir=3D"l=
tr" class=3D"gmail_signature"><div dir=3D"ltr"></div></div></div>

--000000000000d83930057fbd6077--