From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgresql Dev <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru> |
Subject: | time waiting on patch queue |
Date: | 2006-02-16 20:28:21 |
Message-ID: | 43F4E065.7060207@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
[redirecting to -hackers]
Tom Lane wrote:
>At the moment it's not unusual for nontrivial patches to sit around
>for a month or two, unless they happen to attract special interest of
>one of the committers.
>
>
>
>
Yeah. That's just horrible. It makes people lose interest and can hurt
because of bitrot too. I wish we could aim at some maximum time at least
for a first cut review. If there are areas where only one or two people
have sufficient expertise, that's also a worry.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2006-02-16 21:37:53 | Re: how solve diff of API counstruct_md_array between |
Previous Message | Robert Treat | 2006-02-16 20:09:41 | Re: [HACKERS] Patch Submission Guidelines |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2006-02-16 21:37:53 | Re: how solve diff of API counstruct_md_array between |
Previous Message | Robert Treat | 2006-02-16 20:09:41 | Re: [HACKERS] Patch Submission Guidelines |