Re: Deal with <>s in message IDs - Mailing list pgsql-www

From Magnus Hagander
Subject Re: Deal with <>s in message IDs
Date
Msg-id CABUevEzcdynidbBx5RU6gAGY-UFqo6h=-WawsTp0u67tkG6NeA@mail.gmail.com
Whole thread Raw
In response to Re: Deal with <>s in message IDs  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Deal with <>s in message IDs  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-www
<p dir="ltr"><br /> On Oct 30, 2014 1:13 PM, "Alvaro Herrera" <<a
href="mailto:alvherre@2ndquadrant.com">alvherre@2ndquadrant.com</a>>wrote:<br /> ><br /> > Magnus Hagander
wrote:<br/> > > On Thu, Oct 30, 2014 at 12:56 PM, Vik Fearing <vik@xocolatl.community> wrote:<br /> >
>> On 10/30/2014 12:46 PM, Magnus Hagander wrote:<br /> > > >> On Wed, Oct 29, 2014 at 5:28 PM, Jim
Nasby<<a href="mailto:Jim.Nasby@bluetreble.com">Jim.Nasby@bluetreble.com</a>> wrote:<br /> > > >>>
Ifyou're referring to the <> issue, my problem is this: If you paste<br /> > > >>>
'<message-ID>'into commitfest instead of just 'message-ID' you get no<br /> > > >>> results,
becauseit creates a URL that contains the <>s. Obviously<br /> > > >>> commitfest could be taught
tostrip <>, but ISTM it's more useful to have<br /> > > >>> pgarchives do it.<br /> > >
>><br/> > > >> Yeah, I still don't understand what you mean. And I'd still need an<br /> > >
>>example link that shows the wrong thing, both to understand it and to<br /> > > >> verify a
fix..<br/> > > ><br /> > > ><br /> > > > <a
href="http://www.postgresql.org/message-id/%3CCABUevEyy05BHq21BA0CgYcsmvd06ZKXpXPAwr1khZ+RGk+4PUA@mail.gmail.com%3E">http://www.postgresql.org/message-id/%3CCABUevEyy05BHq21BA0CgYcsmvd06ZKXpXPAwr1khZ+RGk+4PUA@mail.gmail.com%3E</a><br
/>> > ><br /> > > > versus<br /> > > ><br /> > > > <a
href="http://www.postgresql.org/message-id/CABUevEyy05BHq21BA0CgYcsmvd06ZKXpXPAwr1khZ+RGk+4PUA@mail.gmail.com">http://www.postgresql.org/message-id/CABUevEyy05BHq21BA0CgYcsmvd06ZKXpXPAwr1khZ+RGk+4PUA@mail.gmail.com</a><br
/>> ><br /> > > Ok, I'm sorry, but I'm still confused here. Where do we actually<br /> > > generate
thefirst link, the one that's wrong? Do we put the wrong<br /> > > thing in our thread browsing somewhere? If so,
I'mstill failing to<br /> > > find it :)<br /> ><br /> > Some people enter message-ids with the < >
delimitersin the commitfest app.<br /> ><br /> > I'm not really sure this really belongs in the archives app.  We
could<br/> > just have the commitfest app remove them on input.<br /> ><p dir="ltr">Oh, now I get it. Yeah, based
onthat it does sound like the wrong place to fix it. Though if it's easy enough it might be worth doing for
convenience.I'll see if there's some place to stick a regexp that can do it safely. <p dir="ltr">/Magnus  

pgsql-www by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Deal with <>s in message IDs
Next
From: Jim Nasby
Date:
Subject: Re: Deal with <>s in message IDs