On 5/23/16 4:42 PM, Conrad Meyer wrote: > On Mon, May 23, 2016 at 4:34 PM, Alan Somers <asom...@freebsd.org> wrote: >> On Mon, May 23, 2016 at 5:13 PM, Bryan Drewery <bdrew...@freebsd.org> wrote: >>> >>> On 5/23/16 1:30 PM, Alan Somers wrote: >>>> UPDATING is updated as of r300539. Any objection to merging this to >>>> stable/10? >>> >>> If any port uses it then yes. Binaries are built from 10.1 and expected >>> to work on 10.1, 10.2, 10.3, 10.4, etc. >> >> >> Most ports that use bitstring should work. The only ports that won't are >> ports that either store bitstrings on disk or transmit them across a network >> without an explicit serialization step. A few other weird cases would break >> too, like building a port on 10.3, updating sys/bitstring.h, then rebuilding >> some object files but not others. Is there any way to figure out what ports >> might be using this header? OpenHub code search didn't turn up anything. > > It seems to me like this is exactly the sort of ABI breakage the > stable/* branches promise not to make.
I just noticed that this is not a library. It's only macros. So I take back what I said. -- Regards, Bryan Drewery _______________________________________________ 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"
