Heavy I/O blocks FreeBSD box for several seconds
sgk at troutmask.apl.washington.edu
Mon Jul 11 22:13:23 UTC 2011
On Mon, Jul 11, 2011 at 05:50:44PM -0400, Arnaud Lacombe wrote:
> On Mon, Jul 11, 2011 at 5:38 PM, Arnaud Lacombe <lacombar at gmail.com> wrote:
> > Hi,
> > On Mon, Jul 11, 2011 at 4:40 PM, Steve Kargl
> > <sgk at troutmask.apl.washington.edu> wrote:
> >> On Mon, Jul 11, 2011 at 04:33:44PM -0400, Arnaud Lacombe wrote:
> >>> For the record, I would like to see enforced public review for _every_
> >>> patch *before* it is checked in, as a strong rule. gcc system is
> >>> particularly interesting. But it is not likely to happen in FreeBSD
> >>> where FreeBSD committers are clearly more free than other at
> >>> checking-in un-publicly-reviewed stuff (especially _bad_ stuff).
> >>> This would of course apply even to long-time committers, no matter how
> >>> it hurt their ego (which I definitively do not care about).
> >> As a long time GCC committer, I think that you have grossly
> >> over-simplified the GCC review process and how a submitted
> >> patch is approved for committing.
> > Yes.
> Just to provide information more information than these sterile mails,
> here is the gcc contribution guidelines:
Which if one reads, one finds http://gcc.gnu.org/svnwrite.html#policies
Localized write permission.
This is for people who have primary responsibility for ports, front
ends, or other specific aspects of the compiler. These folks are
allowed to make changes to areas they maintain and related
documentation, web pages, and test cases without approval from anyone
else, and approve other people's changes in those areas. They must
get approval for changes elsewhere in the compiler.
More information about the freebsd-questions