From owner-freebsd-current Sun Apr 23 11:50:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DC55837BA18; Sun, 23 Apr 2000 11:50:53 -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 UAA45596; Sun, 23 Apr 2000 20:50:10 +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 11:46:34 PDT." <200004231846.LAA63231@apollo.backplane.com> Date: Sun, 23 Apr 2000 20:50:09 +0200 Message-ID: <45594.956515809@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231846.LAA63231@apollo.backplane.com>, Matthew Dillon writes: >:I don't see anything justifying an immediate MFC in this patch. Please >:allow the normal waiting period to elapse before you MFC. > > Unless you can justify a reason for it NOT to be MFC'd immediately, I > see no reason to wait for this particular baby. Sorry, Matt, that is not the way it works. Unless there is an overriding issue, things do not get MFC'ed immediately. You have only cited reasons why it would be much more convenient for you personally to MFC right away, that is not enough to justify an immediate MFC. -- 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-current" in the body of the message