From owner-freebsd-current  Mon Dec 18 04:14:10 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA23171
          for current-outgoing; Mon, 18 Dec 1995 04:14:10 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA23166
          for <current@freebsd.org>; Mon, 18 Dec 1995 04:14:06 -0800 (PST)
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id EAA00783; Mon, 18 Dec 1995 04:14:01 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id EAA00230; Mon, 18 Dec 1995 04:14:04 -0800
Message-Id: <199512181214.EAA00230@corbin.Root.COM>
To: Poul-Henning Kamp <phk@critter.tfs.com>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, current@freebsd.org
Subject: Re: FreeBSD-current-stable ??? 
In-reply-to: Your message of "Mon, 18 Dec 95 09:54:04 +0100."
             <21257.819276844@critter.tfs.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 18 Dec 1995 04:14:03 -0800
Sender: owner-current@freebsd.org
Precedence: bulk

>But anyway, here goes:  I intend to continue to isolate the scope of
>variables as far as I can get it.  This may from time to time make
>a custom kernel uncompilable, as my test-set is GENERIC and LINT.

   Please don't lose sight of the fact that changes like this can very easily
introduce new bugs. Our linker doesn't complain about multiple declarations
of a common symbol...so if these exist, making variables that are supposed to
be common into private/static will introduce "interesting" new bugs.

-DG