Re: Committing a driver to -stable
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. The driver is for ProSum's : ProATM card. I have recently committed a full busdma driver to current : (patm(4)), that I hesitate to backport to -stable because it requires ATM : infrastructure that we don't have in stable. On the other hand there is a : -stable driver for this card from ProSum (www.prosum.fr) that is reported : to be very stable under -stable :-), that several people use and that I : would like to commit. So, can I do this? Yes. The main reason that we try to commit to current first then to stable is to make sure that patches don't get lost when only committed to -stable. since there's a different way of doing the same thing in current, no new functionality will be instantly lost upgrading to current. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Committing a driver to -stable
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 -stable that will not be in -current. The > > driver is for ProSum's ProATM card. I have recently committed a > > full busdma driver to current (patm(4)), that I hesitate to > > backport to -stable because it requires ATM infrastructure that we > > don't have in stable. On the other hand there is a -stable driver > > for this card from ProSum (www.prosum.fr) that is reported to be > > very stable under -stable :-), that several people use and that I > > would like to commit. So, can I do this? > > If the same device is supported under -current already, and it's a > question of how the driver is implemented (i.e., completely > differently in -stable due to a lack of -current's ATM > infrastructure), then I don't see why not. However, you may want > to 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 action. Agreed. I suggest dashing off a copy of your original message to arch@ and follow up to trb@ ONLY IF someone complains. -- "Where am I, and what am I doing in this handbasket?" Wes Peters [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Committing a driver to -stable
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. Nielsen pgp0.pgp Description: PGP signature
Re: Committing a driver to -stable
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 ProSum's > ProATM card. I have recently committed a full busdma driver to current > (patm(4)), that I hesitate to backport to -stable because it requires ATM > infrastructure that we don't have in stable. On the other hand there is a > -stable driver for this card from ProSum (www.prosum.fr) that is reported > to be very stable under -stable :-), that several people use and that I > would like to commit. So, can I do this? > > harti > -- > harti brandt, > http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private > [EMAIL PROTECTED], [EMAIL PROTECTED] If the same device is supported under -current already, and it's a question of how the driver is implemented (i.e., completely differently in -stable due to a lack of -current's ATM infrastructure), then I don't see why not. However, you may want to 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 action. -- Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED] TECHNOkRATIS Consulting Services * http://www.technokratis.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Committing a driver to -stable
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 ProSum's ProATM card. I have recently committed a full busdma driver to current (patm(4)), that I hesitate to backport to -stable because it requires ATM infrastructure that we don't have in stable. On the other hand there is a -stable driver for this card from ProSum (www.prosum.fr) that is reported to be very stable under -stable :-), that several people use and that I would like to commit. So, can I do this? harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
