From owner-freebsd-stable Sat Sep 16 17:39:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4EE1737B422; Sat, 16 Sep 2000 17:39:41 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA62486; Sat, 16 Sep 2000 17:39:41 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 16 Sep 2000 17:39:41 -0700 (PDT) From: Kris Kennaway To: freebsd-stable@freebsd.org Cc: stable@freebsd.org Subject: Re: I'll be rolling a 4.1.1 release on September 25th In-Reply-To: <20000916180737.B2124@pir.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Sep 2000, Peter Radcliffe wrote: > Jordan Hubbard probably said: > > standard configuration, I'll be rolling a network-only patch release > > to 4.1 called 4.1.1. If you therefore have anything to MFC, please > > do the following: > > Can we _please_ get these two patches into at least -stable before or > after this release cut ? Poeple often pop up right before a release is due to be rolled, and ask for some patch to "make it into the release" - often it doesn't, and they go away until the next release is announced. This isn't how the FreeBSD development model works, and you're targetting the wrong group at the wrong time. You need to get your patch applied to *FreeBSD-CURRENT* preferably a month or more before the release, and then get it merged back to -stable. If you do that now then there's a good chance your patches will make it back in time for 4.2 Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message