search for: ee61d232

...e per stable release is good enough (rather than once per API change). We did this correctly for commits b0ce4411/cb309687/df0cc21d (bumping to API version 2 for the combined changes between v1.2 and v1.4), but failed to do so for f184fdc3 (affecting v1.10), 4ca66f70 (affecting v1.12), or 5ee7bd29/ee61d232 (affecting the upcoming v1.14). So do it retroacively now, as well as backporting intermediate bumps to affected stable branches. Signed-off-by: Eric Blake <eblake@redhat.com> --- I'm pushing this soon. include/nbdkit-filter.h | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletion...

...nough (rather than once > per API change). > > We did this correctly for commits b0ce4411/cb309687/df0cc21d (bumping > to API version 2 for the combined changes between v1.2 and v1.4), but > failed to do so for f184fdc3 (affecting v1.10), 4ca66f70 (affecting > v1.12), or 5ee7bd29/ee61d232 (affecting the upcoming v1.14). So do it > retroacively now, as well as backporting intermediate bumps to > affected stable branches. > > Signed-off-by: Eric Blake <eblake@redhat.com> > --- > > I'm pushing this soon. > > include/nbdkit-filter.h | 8 +++++---...

...g incompatible API/ABI changes (see commit 6934d4c1). However, we can't use .version (it was documented as optional, so even though all our in-tree filters set it, a theoretical out-of-tree filter could use NULL; and it has changed offsets in the ABI during previous API changes, such as commit ee61d232). Thus, we have to bump the API version one final time; but now, our API guaarantees enough stable ABI to check the version string as part of our API sanity checking, so we are set to avoid future maintenance snafus. All in-tree filters are affected now that .version is no longer available as an...