Re: Deal with <>s in message IDs

From: Vik Fearing <vik(at)xocolatl(dot)community>
To: Magnus Hagander <magnus(at)hagander(dot)net>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Deal with <>s in message IDs
Date: 2014-10-30 11:56:46
Message-ID: 5452277E.3070701@xocolatl.community
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On 10/30/2014 12:46 PM, Magnus Hagander wrote:
> On Wed, Oct 29, 2014 at 5:28 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> If you're referring to the <> issue, my problem is this: If you paste
>> '<message-ID>' into commitfest instead of just 'message-ID' you get no
>> results, because it creates a URL that contains the <>s. Obviously
>> commitfest could be taught to strip <>, but ISTM it's more useful to have
>> pgarchives do it.
>
> Yeah, I still don't understand what you mean. And I'd still need an
> example link that shows the wrong thing, both to understand it and to
> verify a fix..

http://www.postgresql.org/message-id/%3CCABUevEyy05BHq21BA0CgYcsmvd06ZKXpXPAwr1khZ+RGk+4PUA@mail.gmail.com%3E

versus

http://www.postgresql.org/message-id/CABUevEyy05BHq21BA0CgYcsmvd06ZKXpXPAwr1khZ+RGk+4PUA@mail.gmail.com
--
Vik

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2014-10-30 12:01:12 Re: Deal with <>s in message IDs
Previous Message Magnus Hagander 2014-10-30 11:46:53 Re: Deal with <>s in message IDs