Re: Commit fest queue - Mailing list pgsql-hackers

From Tom Dunstan
Subject Re: Commit fest queue
Date
Msg-id ca33c0a30804100257g63a6f282tf97ad66a98139785@mail.gmail.com
Whole thread Raw
In response to Re: Commit fest queue  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: Commit fest queue  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Re: Commit fest queue  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Thu, Apr 10, 2008 at 3:03 PM, Stefan Kaltenbrunner
<stefan@kaltenbrunner.cc> wrote:

>  well what about having the tracker being subscribed to the list and let it
> create a bug/patch/ticket id automatically for new mails - that way all
> stuff is automatically tracked ? - That way it can be categorized in the
> course of the following discussion but no history gets lost.

I presume you mean for -patches and not -hackers. Even so I reckon
that would create vastly more noise than signal in the eventual
tracker - part of the existing problem has been that wading through
list archives is a pain for someone wanting to know the current status
of a patch. I can't see the above helping that.

Cheers

Tom


pgsql-hackers by date:

Previous
From: Mario Weilguni
Date:
Subject: Re: Setting a pre-existing index as a primary key
Next
From: Thomas Burdairon
Date:
Subject: Re: [JDBC] Re: How embarrassing: optimization of a one-shot query doesn't work