Date: Fri, 11 Mar 2016 09:37:43 -0800 From: Bryan Drewery <bdrewery@FreeBSD.org> To: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: CHANGES file Message-ID: <56E30267.30009@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rXVFvjo6HgSg9DOVkM1MP1MqtB5k9CxgG Content-Type: multipart/mixed; boundary="4U3FcvogfHn0bAHcWffITFjqEvCBflLBq" From: Bryan Drewery <bdrewery@FreeBSD.org> To: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Message-ID: <56E30267.30009@FreeBSD.org> Subject: CHANGES file --4U3FcvogfHn0bAHcWffITFjqEvCBflLBq Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable In ports we have an UPDATING file that is targeted at users and a CHANGES file that is targeted at developers regarding API changes. I would like to introduce a CHANGES file as it makes it simpler for developers to see what has changed without reading through all commit logs. This is of great benefit for module writers and vendors who may even have customized some of the code in the tree. Some examples of recent changes that are otherwise undocumented: 1. r295707 which introduced g_reset_bio() which *currently* is a wrapper around bzero, but may change. At Isilon we had >1 lines of our own code affected by this change and I feel lucky I noticed it rather than leaving it to someone to discover years from now when it matters. 2. A lot of my recent share/mk changes may cause grief for vendors (but not likely out-of-tree builds). 3. callout_stop(9) return value. Note I am not requesting every little KPI change be documented in here. I am only wanting to document ones where a change will break something for someone and no warning or error is given if they do nothing. Many API changes will cause a build error or warning while many do not as they are not expressible in C or not utilized by our style or captured by all compilers (like which return values are possible via enum). Unless someone objects for good reason I will create this file and encourage others to document their subtle changes in it. Of course it will not be 100% but it should be helpful nonetheless. --=20 Regards, Bryan Drewery --4U3FcvogfHn0bAHcWffITFjqEvCBflLBq-- --rXVFvjo6HgSg9DOVkM1MP1MqtB5k9CxgG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJW4wJnAAoJEDXXcbtuRpfPfFsIALKdigY9d2dR40a8beXCXOAn G3EBZLjzzYY6QiZUQRwLI+jQEspmQwAAVTWXtCyrIdKj2UyjCVBNkaElDQ+Y6sXn htUsRNJhW+FbcS9zqwmBn6w4Gb3AUYZw+AijeK+dBJdbA08y0YX4LL3kipNyfNlE ijA8Gb810pbU9KW/OyOV1c4QMXHBhLE7M8jCBrxH6p5qLUPy4s+VNvKSBdXlHLQz rstlqs/iZPRWmNmpERdy1wvfuoyG0XwVgakuZZHSo7gsyJk/YOhZHwgKEvjsBYNY MHLHyESXCXfT1TFry4XUP6pm0kYG966taTQsSLE8EwMFbij9Z0lK84HtpBboRUE= =BhfZ -----END PGP SIGNATURE----- --rXVFvjo6HgSg9DOVkM1MP1MqtB5k9CxgG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56E30267.30009>