From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Deal with <>s in message IDs |
Date: | 2014-10-29 16:28:04 |
Message-ID: | 54511594.8010601@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
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...
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.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2014-10-30 11:46:53 | Re: Deal with <>s in message IDs |
Previous Message | Magnus Hagander | 2014-10-29 10:01:01 | Re: Deal with <>s in message IDs |