Date: Fri, 18 Jul 2003 13:26:20 -0700 From: Wes Peters <wes@softweyr.com> To: Bosko Milekic <bmilekic@technokratis.com>, Harti Brandt <brandt@fokus.fraunhofer.de> Cc: hackers@freebsd.org Subject: Re: Committing a driver to -stable Message-ID: <200307181326.20301.wes@softweyr.com> In-Reply-To: <20030718132827.GC29449@technokratis.com> References: <20030718181018.D972@beagle.fokus.fraunhofer.de> <20030718132827.GC29449@technokratis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 wes@softweyr.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307181326.20301.wes>