Re: Getting a bug tracker for the Postgres project

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Joe Abbate <jma(at)freedomcircle(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Kim Bisgaard <kim+pg(at)alleroedderne(dot)adsl(dot)dk>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Getting a bug tracker for the Postgres project
Date: 2011-05-31 17:13:40
Message-ID: BANLkTinQW6tCSuF8iJsH83JD9G3n5yr2Yw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 31, 2011 at 19:10, Joe Abbate <jma(at)freedomcircle(dot)com> wrote:
> On 05/31/2011 12:41 PM, Kevin Grittner wrote:
>> The point is that the community seems to have reached a consensus
>> that they would rather use this URL for the above message:
>>
>> http://archives.postgresql.org/message-id/20031205173035.GA16741@wolff.to
>
> OK, as I said, I can still capture the message-id's by crawling -bugs by
> year-month.

Just to be clear, crawling the current archives for this info is
probably the easiest part of the whole project. In fact, the majority
of the information you'd need is *already* in a postgresql database on
search.postgresql.org.

So - let's start in the other end, and get back to this if/when it's needed.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ross J. Reedstrom 2011-05-31 17:15:36 Re: [PATCH] Bug in XPATH() if expression returns a scalar value
Previous Message Joe Abbate 2011-05-31 17:10:32 Re: Getting a bug tracker for the Postgres project