From owner-freebsd-current  Wed Jul  1 10:42:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA20617
          for freebsd-current-outgoing; Wed, 1 Jul 1998 10:42:52 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from sos@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA20610;
          Wed, 1 Jul 1998 10:42:46 -0700 (PDT)
          (envelope-from sos)
Message-Id: <199807011742.KAA20610@hub.freebsd.org>
Subject: Re: opt_linux.h, opt_nfs.h, and friends
In-Reply-To: <199807011634.MAA04510@pcnet1.pcnet.com> from Daniel Eischen at "Jul 1, 98 12:34:44 pm"
To: eischen@vigrid.com (Daniel Eischen)
Date: Wed, 1 Jul 1998 10:42:46 -0700 (PDT)
Cc: freebsd-current@FreeBSD.ORG, rcarter@pinyon.org
From: sos@FreeBSD.ORG
Reply-to: sos@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In reply to Daniel Eischen who wrote:
> > My make buildworld this morning ~6:30AM MST fails in lkm/linux
> > looking for an opt_linux.h.  Touching the file in the
> > obj hierarchy gets through lkm/linux but then the build
> > fails looking for opt_nfs.h and couple of others (going
> > from memory, which erodes yearly...).
> >
> > Now I just re-cvsupped all my sources last night, but this
> > is only a couple of day old -current.  Not seeing any
> > complaints in current or fixes in cvs-all makes me
> > suspect something on my side.  What am I missing?
> 
> I got the same thing from a CVSup on 6/30/98(last night).
> I re-CVSup'd this morning, and will try again later, but
> you're not alone.

I think Bruce has just fixed those bogons...

This is the X'd time lately that current has been broken for days.
I can accept that there can be runtime erros/bugs in new code, its
very difficult to check for all situation s given maybe only one
machine to test it on.
BUT, there is absolutely NO excuse for committing code that
wont even compile..

Maybe we need to reconsider the whole commiters/access scenario...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt             (sos@FreeBSD.org)             FreeBSD Core Team
               So much code to hack -- so little time.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message