Re: [HACKERS] pull raw text of a message by message-id

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "w^3" <pgsql-www(at)postgresql(dot)org>
Subject: Re: [HACKERS] pull raw text of a message by message-id
Date: 2009-06-28 01:49:51
Message-ID: 603c8f070906271849x17ef9f81g853877eead16e63b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

On Thu, Jun 4, 2009 at 5:53 PM, Alvaro
Herrera<alvherre(at)commandprompt(dot)com> wrote:
> Bruce Momjian escribió:
>> Alvaro Herrera wrote:
>> > Robert Haas escribi?:
>> >
>> > > Oh, this is awesome.  It would be handy to include a link on the HTML
>> > > version of the page for when people are trying to pull down a patch
>> > > that someone has foolishly included in the body of the email rather
>> > > than attaching it.
>> >
>> > There already is one :-)  Look at the headers -- after the Message-Id there is
>> > a link which says "text/plain".
>>
>> I don't see a text/plain option on this page:
>>
>>       http://archives.postgresql.org/pgsql-hackers/2009-05/msg00466.php
>>
>> Why?
>
> Argh.  I think this whole thing died when I fixed the bug about
> message-id links in the message body being mangled reported by Tom, some
> days ago.  The Message-id links are now being generated internally by
> Mhonarc instead of your script ...
>
> I don't think it's difficult to fix this problem but I don't have time
> to do it right now :-(
>
> (Maybe it's time I bit the bullet and stopped kludging the Mhonarc
> install all over the place and instead spent some time on the new
> archives code ...)

I see that this has been fixed, but should I count on it staying
fixed? My original motivation for asking for it was to integrate it
into the CommitFest management tool I've been hacking on
(http://coridan.postgresql.org/), but I probably don't want to do that
if it's apt to break frequently.

One suggestion: Could you make it return a 404 error if the message ID
is unknown, rather than 200 OK and a body of "not found"?

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Reini Urban 2009-06-28 13:33:27 Re: stat() vs cygwin
Previous Message Tom Lane 2009-06-26 23:25:13 Re: Join optimization for inheritance tables

Browse pgsql-www by date

  From Date Subject
Next Message Robert Haas 2009-06-28 02:06:36 Re: Stuck cvs lock on anoncvs repository
Previous Message Marc G. Fournier 2009-06-28 00:09:19 Re: Stuck cvs lock on anoncvs repository