From owner-freebsd-security Thu Oct 5 15:39:15 2000 Delivered-To: freebsd-security@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 89F2137B503; Thu, 5 Oct 2000 15:39:02 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95McUX01279; Thu, 5 Oct 2000 15:38:34 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Robert Watson Cc: John Baldwin , Brett Glass , freebsd-security@FreeBSD.org, cvs-committers@FreeBSD.org, Paul Richards , "David O'Brien" , Ralph Huntington Subject: Re: Stable branch In-Reply-To: Message from Robert Watson of "Thu, 05 Oct 2000 15:37:46 EDT." Date: Thu, 05 Oct 2000 15:38:29 -0700 Message-ID: <1275.970785509@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1) Increased scrutiny of MFC's in advance so that there's less chance of That's perhaps doable, though others have already commented on the difficulties of getting "scrutiny" before the fact in this project so I won't belabor the point. > 2) Make release tags into branches, so that ERRATA and other relevant That scares me. I don't like the idea of n-way merges. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message