From owner-freebsd-stable Sat Sep 16 18:19:13 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 253D537B424 for ; Sat, 16 Sep 2000 18:19:09 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA70410 for ; Sat, 16 Sep 2000 18:19:09 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 16 Sep 2000 18:19:08 -0700 (PDT) From: Kris Kennaway To: freebsd-stable@freebsd.org Subject: Re: I'll be rolling a 4.1.1 release on September 25th In-Reply-To: <20000916205417.F2124@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: > Kris Kennaway probably said: > > On Sat, 16 Sep 2000, Peter Radcliffe wrote: > > > 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 > > Sorry for being short, but I'm on my way out. > > 1) they're not my patches, but they're useful to me. > > 2) I didn't specificly ask for them to make it into this release, I > said "before or after". > > 3) I've asked before and go no response. > > 4) I can't commit things to -current. My point was that you need to either ask one of the committers directly, or ask in a forum where the committerss hang out. Thats not -stable - there are only a few of us here, so asking here is almost akin to asking in a vacuum. > 5) I know how the system works, but it requires someone to commit > the patches and no one will. Works for you..they have to go through -current first in case they break for someone else. > 6) Please watch your destination, that mail went to > freebsd-stable@freebsd.org and stable@freebsd.org. Your original mail had this: Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: stable@freebsd.org > 7) One of the other patches was usb related and has already been > committed and MFCed because it was assigned to someone who did > something about it. Good :-) > My question still stands, can these patches get in, somewhere ? You're still talking to the wrong list. 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