From owner-freebsd-bugs  Sat Dec 30 19:51:53 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA04456
          for bugs-outgoing; Sat, 30 Dec 1995 19:51:53 -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 TAA04447
          for <freebsd-bugs@freebsd.org>; Sat, 30 Dec 1995 19:51:49 -0800 (PST)
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id TAA16472; Sat, 30 Dec 1995 19:51:48 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id TAA01016; Sat, 30 Dec 1995 19:51:49 -0800 (PST)
Message-Id: <199512310351.TAA01016@corbin.Root.COM>
To: "David J. Fiander" <davidf@mks.com>
cc: freebsd-bugs@freebsd.org
Subject: Re: kern/921: 
In-reply-to: Your message of "Sat, 30 Dec 95 19:31:51 PST."
             <199512310331.TAA00278@corbin.Root.COM> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 30 Dec 1995 19:51:33 -0800
Sender: owner-bugs@freebsd.org
Precedence: bulk

>>BTW, any particular reason that the fix for kern/788 (fixed in 1.13
>>of kern_resource.c) didn't make it into 2.1.0-RELEASE, which contains
>>1.12 of kern_resource.c?
>
>   Because it was a moving target (see rev 1.14) and because it was made
>immediately before the 2.1 release. As a general policy, only critical
>bugfixes that have a scope that is easily determined are brought into the
>release tree.

   BTW, are you suggesting that rev 1.13/1.14 fixes the problem you're
reporting?

-DG