From owner-freebsd-commit  Tue Sep 19 04:34:35 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id EAA27282
          for freebsd-commit-outgoing; Tue, 19 Sep 1995 04:34:35 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id EAA27270
          for cvs-all-outgoing; Tue, 19 Sep 1995 04:34:32 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id EAA27258
          for cvs-etc-outgoing; Tue, 19 Sep 1995 04:34:30 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA27250
          ; Tue, 19 Sep 1995 04:34:20 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id EAA01886; Tue, 19 Sep 1995 04:34:14 -0700
Date: Tue, 19 Sep 1995 04:34:14 -0700
Message-Id: <199509191134.EAA01886@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: paul@freebsd.org, CVS-commiters@freebsd.org, cvs-etc@freebsd.org
In-reply-to: <11199.811509858@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: cvs commit: src/etc rc sysconfig
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-commit@freebsd.org
Precedence: bulk

 * Woog.  This is getting a bit crazy.  Can we have maybe just a little
 :
 * was decided to take a route similar to what we have now.  I'd have to
 * bring it all back in again.
 * 
 * Maybe if I simply remove it from the snapshot?  That would, at least,
 * prevent anyone from becoming attached to a feature that might go away.
 * We could leave it in -current for a little longer then, until this
 * is decided..

Ok, please do that then.  But I request no port use this mechanism
until the issue is resolved, it may be in -current, but it's as dead
as a frozen chicken for now (i.e., until it's thawed).

Satoshi