Re: Deal with <>s in message IDs

On Wed, Oct 29, 2014 at 5:28 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 10/29/14, 5:01 AM, Magnus Hagander wrote:
>>
>> On Wed, Oct 29, 2014 at 12:17 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
>> wrote:
>>>
>>> Thunderbird (and presumably other things) will wrap message IDs in <>s,
>>> which pgarchives doesn't handle correctly. I'd like to fix this;
>>> presumably
>>> the correct way to do so is the same way we're handling /'s in message
>>> IDs?
>>
>>
>> Um. So what does it actually do :) Do you have an example?
>
>
> The backslash stuff? I don't know, I was hoping you did...

There's a backslash thing as well?

> 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..

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/