From owner-freebsd-security Tue Jan 25 9:27: 4 2000 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 796AC15269 for ; Tue, 25 Jan 2000 09:26:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA06497; Tue, 25 Jan 2000 10:26:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA04563; Tue, 25 Jan 2000 10:26:22 -0700 (MST) Message-Id: <200001251726.KAA04563@harmony.village.org> To: geniusj Subject: Re: Merged patches Cc: security@FreeBSD.ORG In-reply-to: Your message of "Tue, 25 Jan 2000 17:14:33 EST." References: Date: Tue, 25 Jan 2000 10:26:22 -0700 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message geniusj writes: : This patch does not seem to apply, using 3.4-STABLE branch did patch < : kern.patch from /sys, it applies, but many hunks failed.. Will this be the : official patch? You were the one working on it, no? :) This patch is for -current only. If a different one is needed for stable, we'll deal with that then. We're 3 days from code freeze, and I want to get something good into 4.0 to help limit the damage here. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message