From owner-freebsd-hackers  Sun Oct 13 20:21:05 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA21678
          for hackers-outgoing; Sun, 13 Oct 1996 20:21:05 -0700 (PDT)
Received: from dyson.iquest.net ([198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA21673
          for <hackers@freebsd.org>; Sun, 13 Oct 1996 20:21:02 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA22718; Sun, 13 Oct 1996 22:20:39 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199610140320.WAA22718@dyson.iquest.net>
Subject: Re: Setting Up a Kernel Hacking Machine
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Sun, 13 Oct 1996 22:20:38 -0500 (EST)
Cc: chiuk@cs.indiana.edu, hackers@freebsd.org
In-Reply-To: <199610140205.LAA11038@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 14, 96 11:34:58 am
Reply-To: dyson@freebsd.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> As a general rule, -current is stable enough for development.  If you
> lurk on the -current list and avoid building new kernels for a day or
> so after people like John make major changes, it's actually very good.
> 
I generally agree with that.  We (I) do need help when I have made large
VM changes though.  I am going to resurrect my policy of warning people
a day or so before any risky changes.  When I do warn people, I really
don't mind when they ask for me to put them off for a day or so.

John