On Fri, Jan 14, 2022 at 1:59 AM William A Rowe Jr wrote:
>
> A quick review of nm against libapr-1.so between 1.7.0 and 1.7.x
> indicates that 1.7.1
> isn't releasable as-is. Any hints?
>
> +T apr_pool_find
> +T apr_pool_join
> +T apr_pool_lock
> +T apr_pool_num_bytes
These should have
On Sat, Jan 15, 2022 at 4:37 AM Yann Ylavic wrote:
>
> On Sat, Jan 15, 2022 at 2:00 AM William A Rowe Jr wrote:
> >
> At this point I question the relevance of releasing 1.7.1 at all, I
> think most people will be interested in 1.8.0 and I'd advise distros
> to upgrade to that too. Who will be
On Sat, Jan 15, 2022 at 2:00 AM William A Rowe Jr wrote:
>
> On Fri, Jan 14, 2022 at 5:07 AM Yann Ylavic wrote:
> >
> > On Fri, Jan 14, 2022 at 1:59 AM William A Rowe Jr wrote:
> > >
> > > A quick review of nm against libapr-1.so between 1.7.0 and 1.7.x
> > > indicates that 1.7.1
> > > isn't
On Fri, Jan 14, 2022 at 5:07 AM Yann Ylavic wrote:
>
> On Fri, Jan 14, 2022 at 1:59 AM William A Rowe Jr wrote:
> >
> > A quick review of nm against libapr-1.so between 1.7.0 and 1.7.x
> > indicates that 1.7.1
> > isn't releasable as-is. Any hints?
> >
> > +T apr_pool_find
> > +T apr_pool_join
>
[plus [1] and [2] links..]
On Fri, Jan 14, 2022 at 12:06 PM Yann Ylavic wrote:
>
> On Fri, Jan 14, 2022 at 1:59 AM William A Rowe Jr wrote:
> >
> > A quick review of nm against libapr-1.so between 1.7.0 and 1.7.x
> > indicates that 1.7.1
> > isn't releasable as-is. Any hints?
> >
> > +T
On Fri, Jan 14, 2022 at 1:59 AM William A Rowe Jr wrote:
>
> A quick review of nm against libapr-1.so between 1.7.0 and 1.7.x
> indicates that 1.7.1
> isn't releasable as-is. Any hints?
>
> +T apr_pool_find
> +T apr_pool_join
> +T apr_pool_lock
> +T apr_pool_num_bytes
Those come from r1863234
A quick review of nm against libapr-1.so between 1.7.0 and 1.7.x
indicates that 1.7.1
isn't releasable as-is. Any hints?
+T apr_pool_find
+T apr_pool_join
+T apr_pool_lock
+T apr_pool_num_bytes
+T apr__pool_unmanage
Preserving whatever has changed on 1.8.x branch for ABI breaking changes.
On
