From owner-freebsd-security  Mon Dec 16 10:33:05 1996
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id KAA23187
          for security-outgoing; Mon, 16 Dec 1996 10:33:05 -0800 (PST)
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA23181
          for <freebsd-security@freebsd.org>; Mon, 16 Dec 1996 10:33:01 -0800 (PST)
Received: (from guido@localhost) by gvr.win.tue.nl (8.8.4/8.8.2) id TAA25027; Mon, 16 Dec 1996 19:32:07 +0100 (MET)
From: Guido van Rooij <guido@gvr.win.tue.nl>
Message-Id: <199612161832.TAA25027@gvr.win.tue.nl>
Subject: Re: why is -stable not secure?
In-Reply-To: <199612161654.IAA16978@freefall.freebsd.org> from Adam Kubicki at "Dec 16, 96 05:59:06 pm"
To: mikee@solozzo.tele.pw.edu.pl (Adam Kubicki)
Date: Mon, 16 Dec 1996 19:32:07 +0100 (MET)
Cc: freebsd-security@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Adam Kubicki wrote:
> hi,
> 
> I'd like to ask why patches included in -current aren't in -stable
> version? There are few serious bugs (security too) fixed in -current but not
> in -stable. How long it takes to move patches to -stable source tree??
> 

Normally they are fixed in both. The recent cron things have been overlooked
unfortunately. 

-Guido