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

From Bruce Momjian
Subject Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >
Date
Msg-id 200803121427.m2CER6h09649@momjian.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Magnus Hagander wrote:
> 
> > > It's not. And I personally don't think it would be a problem.
> > > But I think it'll be a lot easier to sell to those who prefer
> > > textfiles in cvs (hello bruce!) if we can.
> > 
> > I don't care who edits it myself, though I can say I get perhaps one
> > patch a year to the TODO list file --- usually I just an email saying
> > remove that item or something.
> 
> Personally I've wished to enter something in the TODO list myself but
> refrained because it was "your area".  Having a derived HTML page
> doesn't make me feel any better -- how should I generate it to ensure
> that my output is equal to yours?

If you change the text file, I will see the CVS update and update the
HTML --- I will never lose a change because my CVS sees your changes.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >
Next
From: Tom Lane
Date:
Subject: Re: [NOVICE] encoding problems