Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > > - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > >
Date
Msg-id 28354.1204926917@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > >  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > >
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Alvaro Herrera wrote:
>> Why do we keep the TODO file with the source code?  Wouldn't it make
>> more sense to store it separately?

> No idea --- it has always been there because it relates directly to the
> source.

I kinda like the fact that the diffs get posted to pgsql-committers;
it provides an easy chance to complain if the TODO description is off
base, which isn't too unusual.

What I'd like to have taken out of CVS is all the FAQs ... I find the
diff traffic on those to be noise.  But others probably see that
differently.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Maximum statistics target
Next
From: Robert Lor
Date:
Subject: Re: Commitfest process