Skip site navigation (1) Skip section navigation (2)

Re: How can I check the treatment of bug fixes?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, MauMau <maumau307(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: How can I check the treatment of bug fixes?
Date: 2011-05-27 17:55:42
Message-ID: BANLkTimMjgooV6LmAO08JNwmsbUMYN-xZA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, May 27, 2011 at 12:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> You have done what you need to do to check the status. Someone who knows
>> something about the bug should speak up at some point.
>
> That patch is waiting for a committer who knows something about Windows
> to pick it up.

It might be useful, in this situation, for the OP to add this patch to
the CommitFest application.

https://commitfest.postgresql.org/action/commitfest_view/open

Also, I think it's about time we got ourselves some kind of bug
tracker.  I have no idea how to make that work without breaking
workflow that works now, but a quick survey of my pgsql-bugs email
suggests that this is far from the only thing slipping through the
cracks.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-05-27 18:11:29
Subject: Re: Vacuum, visibility maps and SKIP_PAGES_THRESHOLD
Previous:From: Steve SingerDate: 2011-05-27 17:06:33
Subject: Re: dblink crash on PPC

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group