Re: inclusions WAS: Increased company involvement - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: inclusions WAS: Increased company involvement
Date
Msg-id 4278DFFD.3010102@familyhealth.com.au
Whole thread Raw
In response to Re: inclusions WAS: Increased company involvement  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: inclusions WAS: Increased company involvement  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
> Yup, and *everyone* with commit accesss has access to *everything* ... I 
> could intruduce a 1 bit change to one of the kernel sources and there is 
> a chance that nobody would ever notice it ... and this includes (or, at 
> least, the last time I did any work) port committers ...

Using cvsacls could deal with that particular problem.  Take the PHP 
project's 1500 committers, and how they can only modify particular files.

Of course, having 1500 committers has made PHP a steaming pile of junk, 
so don't think I support that :)

Being a committer is like that famous saying, "I would never join any 
club that would have me as a member" :D

Chris


pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: inclusions WAS: Increased company involvement
Next
From: "Marc G. Fournier"
Date:
Subject: Re: inclusions WAS: Increased company involvement