Date: Sun, 14 Dec 1997 07:23:43 +0100 (MET) From: Luigi Rizzo <luigi@labinfo.iet.unipi.it> To: mike@smith.net.au (Mike Smith) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed code merge, objections? Message-ID: <199712140623.HAA01235@labinfo.iet.unipi.it> In-Reply-To: <199712140736.SAA05671@word.smith.net.au> from "Mike Smith" at Dec 14, 97 06:06:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > -stable is not meant to accumulate new features from -current. Unless > > > there are strong reasons, new drivers should not migrate there. This > > > _is_ official policy. > > Particularly in the case of Jamil's driver, which is unlikely to be > particularly useful to anyone other than Jamil as anything other than a > sample. Still, it has a purpose. When I have a new piece of hardware I often have to go to Linux to find a driver (i.e. some source code documenting how to use it). > If a feature is nonintrusive and subject to popular demand, migration > after a vetting period in -current is worth considering. Also bear in > mind that often things would make it back to -stable if there was > someone that was a) using the feature and b) had the time and resources > (eg. a -stable system) to do the backport with. Jamil is doing a) and b), but I concede that in this case there might not be popular demand. Cheers Luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712140623.HAA01235>