Re: Committing a driver to -stable

2003-07-19 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Harti Brandt <[EMAIL PROTECTED]> writes: : : Hi all, : : as far as I know new stuff should be first committed to -current and, if : it turns out stable enough, MFCed to -stable. I would like to commit a : driver to -stable that will not be in -current.

Re: Committing a driver to -stable

2003-07-18 Thread Wes Peters
On Friday 18 July 2003 06:28, Bosko Milekic wrote: > On Fri, Jul 18, 2003 at 06:19:46PM +0200, Harti Brandt wrote: > > Hi all, > > > > as far as I know new stuff should be first committed to -current > > and, if it turns out stable enough, MFCed to -stable. I would like > > to commit a driver to -s

Re: Committing a driver to -stable

2003-07-18 Thread Simon L. Nielsen
On 2003.07.18 13:28:27 +, Bosko Milekic wrote: [CUT] > wait for someone from the TRB (is there a list of who's part of this > group somewhere, anyway?) and/or -core to respond before you take There is a list with the TRB members at http://www.freebsd.org/internal/staff.html . -- Simon L

Re: Committing a driver to -stable

2003-07-18 Thread Bosko Milekic
On Fri, Jul 18, 2003 at 06:19:46PM +0200, Harti Brandt wrote: > > Hi all, > > as far as I know new stuff should be first committed to -current and, if > it turns out stable enough, MFCed to -stable. I would like to commit a > driver to -stable that will not be in -current. The driver is for ProS