| From: | "Tom Dunstan" <pgsql(at)tomd(dot)cc> |
|---|---|
| To: | "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commit fest queue |
| Date: | 2008-04-10 09:57:38 |
| Message-ID: | ca33c0a30804100257g63a6f282tf97ad66a98139785@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 10, 2008 at 3:03 PM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-04-10 10:11:29 | Re: Commit fest queue |
| Previous Message | Thomas Burdairon | 2008-04-10 09:47:36 | Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work |