From owner-cvs-etc  Wed Jun  4 18:48:52 1997
Return-Path: <owner-cvs-etc>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA26463
          for cvs-etc-outgoing; Wed, 4 Jun 1997 18:48:52 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26456;
          Wed, 4 Jun 1997 18:48:39 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id LAA26835; Thu, 5 Jun 1997 11:34:36 +1000
Date: Thu, 5 Jun 1997 11:34:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199706050134.LAA26835@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au
Subject: Re: cvs commit: src/etc/mtree BSD.include.dist
Cc: ache@nagual.pp.ru, asami@cs.berkeley.edu, bde@zeta.org.au,
        cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-etc@FreeBSD.ORG
Sender: owner-cvs-etc@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> Updating your include files, both directly in /usr/include and in its
>> subdirectories, is just plain something you should do if you're
>> dinking around with sources and building your own kernels and such.  I
>
>OK, so we expect to see a new makefile rule at the top level of the
>kernel source tree that will copy all the includes to the relevant
>places under /usr/include?

No.  Putting it at the top level doesn't help at low levels.  Otherwise,
the standard rules in /usr/src/include/Makefile are sufficient
(cd /usr/src/include; make; make install).  Isn't this how everyone
keeps their include files up to date? :-)

Bruce