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 200803121322.m2CDMgb23799@momjian.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >  ("Magnus Hagander" <magnus@hagander.net>)
Responses Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >
List pgsql-hackers
Magnus Hagander wrote:
> 
> > > How about we move it to the wiki. AFAIK we can still lock it down to who
> > > can edit it if we want to
> >
> > You should confirm you can get the editing granularity you want before
> > making too many plans here if this is important.  The features for locking
> > down things in Mediawiki are very limited.
> >
> > The Wiki philosophy here is that you could revert quite a few bad changes
> > in the time it would take you to lock it down so those bad changes could
> > never happen in the first place.  Last time I checked vandalism and bad
> > edits were not a problem on the developer's wiki.
> 
> 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.

-- 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: Gregory Stark
Date:
Subject: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > >
Next
From: Alvaro Herrera
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >