On Fri, 2018-03-09 at 11:02 +0000, Alexey Dokuchaev wrote: > On Wed, Mar 07, 2018 at 02:53:49PM -0800, Eitan Adler wrote: > > > > On 7 March 2018 at 09:37, John Baldwin <j...@freebsd.org> wrote: > > > > > > ... > > > I suspect many of these changes for iwm, etc. are all intertwined > > > so I'm not sure if you can leave out individual ones. > > Possibly. I do have iwm working on my laptop though. I also know of > > one open PR assigned to me w.r.t. a model I don't own. I'll be > > addressing it some time this week. > I often have mixed feelings when I see lots of similar changes (i.e. > that make up for better hardware support, esp. on a laptop) MFCed. > I'd rather see laptop users run -CURRENT and leave -STABLE branches > for very conservative (server?) users who can't/don't want to afford > the risks of running -CURRENT or require ABI stability in a really > long run, rather than binge-merging things. :-) > > By default it should be -CURRENT all over; it's a very good thing > that we as a Project ourselves are doing this as part of our own > dogfood eating strategy. > > ./danfe >
Some of us have to use our freebsd machines to earn a living, and we can't afford the time and resources to set our jobs aside and debug our working machines on a daily basis. We have the same right to use an up to date and stable OS as "very conservative server users". Discouraging MFCs because your opinion is that everyone should run current is, not to put too fine a point on it, 'totally f'ing crazy'. -- Ian _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
