Date: Thu, 27 Dec 2012 13:38:09 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Cc: src-committers@freebsd.org, svn-src-stable@freebsd.org, svn-src-all@freebsd.org, Alfred Perlstein <bright@mu.org>, svn-src-stable-9@freebsd.org, Konstantin Belousov <kostikbel@gmail.com> Subject: Re: svn commit: r244663 - stable/9 Message-ID: <CAJ-Vmokm6t3smLTONLOSN%2Bdfm50LY4AdqgCXeh8S8aRZDWTjNA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1212251911360.56707@fledge.watson.org> References: <201212241422.qBOEMrcF021632@svn.freebsd.org> <CAJ-VmokV-JL_xZ9otRXubKZ8KQKe7GgLuLU3UMij0HUD_KhCNw@mail.gmail.com> <50D8B533.8080507@mu.org> <20121225104422.GB53644@kib.kiev.ua> <alpine.BSF.2.00.1212251911360.56707@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It's an interesting discussion to have (after the new year, of course.) I understand that we sometimes have to change ABIs because we can't fix problems otherwise. However, I don't recall seeing much/any discussion about this. If it appeared on a list that I didn't spot then cool. But any kind of ABI change in a stable branch deserves a little more discussion before its done. The reason ath(4) 802.11n support isn't in -9 is because of the ABI changes I'd have to do to net80211 (at least) before I could put it in, and I want to make sure all of my changes are in place before I do (hopefully one, maybe two) large-scale changes. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmokm6t3smLTONLOSN%2Bdfm50LY4AdqgCXeh8S8aRZDWTjNA>