From owner-freebsd-current  Thu Jul  2 07:19:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA29675
          for freebsd-current-outgoing; Thu, 2 Jul 1998 07:19:30 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from sos@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA29647;
          Thu, 2 Jul 1998 07:19:23 -0700 (PDT)
          (envelope-from sos)
Message-Id: <199807021419.HAA29647@hub.freebsd.org>
Subject: HEADS UP, IMPORTANT!!
To: current@FreeBSD.ORG (FreeBSD current), committers
Date: Thu, 2 Jul 1998 07:19:22 -0700 (PDT)
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


So, I took yet another sweep at getting world to build again, *SIGH*

Can I kindly demand that people TEST their patches before committing
to the tree, please!

It is mandatory to secure that things still compile after a change,
the least is a recompile of the given program if the change is
located only to a specific part of the tree, and if the change
is to multiple targets, a complete make world has to survive
before committing the changes.

If we cannot get this into shape, so -current at least compiles,
then we will have to start putting more restrictions on what
goes into the tree, and who has access to the crown jewels.

I hope this gets the message across, it would be sad if we
had to start restricting the tree, just because of laziness...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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