Re: [HACKERS] Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >

2008-03-12 Thread Bruce Momjian
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 myse

Re: [HACKERS] Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >

2008-03-12 Thread Alvaro Herrera
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

Re: [HACKERS] Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >

2008-03-12 Thread Bruce Momjian
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 > >

Re: [HACKERS] Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >

2008-03-12 Thread Magnus Hagander
> > 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