This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] dlfcn: Guard __dlerror_main_freeres with __libc_once_get (once) [BZ#24476]

On Wed, 2019-05-15 at 16:38 -0400, Carlos O'Donell wrote:
> On 5/15/19 3:50 PM, Mark Wielaard wrote:
> > Makes sense. Done as follows:
> 
> Perfect. Looks good to me.
> 
> Please commit to master.

Thanks. Done.

I also cherry-picked the commit to release/2.28/master and
release/2.29/master. It applies cleanly and testing shows it fixes the
bug.

I am not entirely clear on the procedure to get them officially
included in the release branches. Can I just commit the cherry-picked
commits and email libc-stable about it? Or should the 2.28 and 2.29
release managers first ack the patch? Do I need to update the NEWS bugs
sections too (master doesn't have a NEWS bugs section).

Thanks,

Mark
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]