From owner-freebsd-current  Sun Dec 17 21:08:02 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA02418
          for current-outgoing; Sun, 17 Dec 1995 21:08:02 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA02364
          Sun, 17 Dec 1995 21:07:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id VAA10399; Sun, 17 Dec 1995 21:03:52 -0800
To: Bruce Evans <bde@zeta.org.au>
cc: andreas@knobel.gun.de, julian@jhome.dialix.com, cracauer@wavehh.hanse.de,
        current@freebsd.org, hackers@freebsd.org, jkh@freebsd.org
Subject: Re: FreeBSD-current-stable ??? 
In-reply-to: Your message of "Mon, 18 Dec 1995 06:11:27 +1100."
             <199512171911.GAA17231@godzilla.zeta.org.au> 
Date: Sun, 17 Dec 1995 21:03:51 -0800
Message-ID: <10396.819263031@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
Precedence: bulk

> >> Hi FreeBSD core team !
> >> 
> >> [ Possibly I'm speaking for many other people here ]
> >It's possible.
> 
> Possibly for non-developers :-).

I think that's something of a cheap shot.  Even developers aren't
always blessed with a surfeit of hardware.  I mentioned that I myself
had been somewhat "scared away" from -current, namely because the only
machine I have available for running -current is also my gateway
machine, and if it starts crashing I'm off the air.  I like being able
to run current and see what people are up to, helping out if I can,
but I can't afford to be radically destabilised by it, and I think a
lot of other folks are saying here that they can't either.

					JOrdan