Re: missing ML messages
От | Magnus Hagander |
---|---|
Тема | Re: missing ML messages |
Дата | |
Msg-id | CABUevEzYdfJ1pvreTM77xspNpnf5qko-_aMoLh+kC7Wdz6Gz6g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: missing ML messages (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: missing ML messages
(Chapman Flack <chap@anastigmatix.net>)
|
Список | pgsql-www |
On Sun, Jan 9, 2022 at 8:35 PM Justin Pryzby <pryzby@telsasoft.com> wrote: > > On Sun, Jan 24, 2021 at 02:37:33PM +0100, Magnus Hagander wrote: > > On Sat, Jan 23, 2021 at 4:14 AM Justin Pryzby <pryzby@telsasoft.com> wrote: > > > On Fri, Jan 22, 2021 at 10:07:38PM -0500, Tom Lane wrote: > > > > Justin Pryzby <pryzby@telsasoft.com> writes: > > > > > I noticed that one of my messages never made it to the HTTP page: > > > > > 20210119190720.GL8560@telsasoft.com > > > > > > > > I see it in the archives, and in my local mail folder too. > > > > https://www.postgresql.org/message-id/20210119190720.GL8560@telsasoft.com > > > > > > Ok...I must have entered it wrong somehow. > > > > > > So the problem is that it doesn't show up here: > > > https://www.postgresql.org/message-id/flat/20170907194236.4cefce96%40wp.localdomain > > > > > > Is it because I used two IDs in reply-to headers? > > > > > > In-Reply-To: <CAFiTN-updTo3aB+7vsECHOHpjB23Av5OfgZQrt90Q33gFK-oZQ@mail.gmail.com> > > > <CAFiTN-utJPbTLQ9i10wT_zmHX=un+RQMB1B1xbkTgrh971vqjw@mail.gmail.com> > > > > > > In mutt, I would've 't'agged two messages, and then ';'-'r' to reply and quote both. > > > > Yeah, I think that's it. We only parse a single value in the in-reply-to. > > I wondered if you've tried to address this ? I have not personally had time to look into it, no (I assume you meant this for me, even though you addressed it primarily to Champan, who previously did not participate in the thread). And apparently neither has anybody else. > + Chapman Flack, who wrote: > > https://www.postgresql.org/message-id/61C09C1D.5050702@anastigmatix.net > > *seeing that RFC 5322 3.6.4 permits more than one msg-id for in-reply-to, > > crosses fingers to see what PGLister will make of it* It should be noted that pglister does exactly nothing with it and should pass it through without making any changes whatsoever. The question is what happens when it hits the archives, which are not part of pglister. Which of course still needs to be handled. A first step would probably be to figure out *what* to do. The RFC basically appears to punt on the whole idea of what to do with multiple parents. I'm unsure what would be the best thing for pglister to do. Just pick the first entry and go with that? That would certainly be the easiest, but would it be correct? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
В списке pgsql-www по дате отправления:
Предыдущее
От: Magnus HaganderДата:
Сообщение: Re: [PATCHES] pglister: make organization name generic