From owner-freebsd-stable Sun Apr 23 12: 6:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id F3E3237B690; Sun, 23 Apr 2000 12:06:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA45716; Sun, 23 Apr 2000 21:05:41 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 12:01:46 PDT." <200004231901.MAA63381@apollo.backplane.com> Date: Sun, 23 Apr 2000 21:05:41 +0200 Message-ID: <45714.956516741@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231901.MAA63381@apollo.backplane.com>, Matthew Dillon writes: > I'm sorry, Poul, but you are going to have to come up with better > reasoning then that. > > Not all changes committed to -current require a waiting period before > being MFC'd to stable. Specifically, simple and obvious bug fixes > certainly do not need a waiting period. Matt, This does not apply to your patch. The "simple and obvious" loophole applies to spelling fixes and similar, not to anything which changes behaviour of the system. Your current patch does not qualify for immediate MFC status unless the security officer says so. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message