This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] dlfcn: Guard __dlerror_main_freeres with __libc_once_get (once) [BZ#24476]
On 5/16/19 9:06 AM, Florian Weimer wrote:
> * Mark Wielaard:
>
>> 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?
>
> Yes, that's fine. Please use cherry-pick -x and edit the NEWS file
> manually to include a line for the bug. Maybe tweak the commit message
> to get the bug notification, too.
Mark,
For the record the policy is documented here in our Release policy:
https://sourceware.org/glibc/wiki/Release/#General_policy
~~~
Patch backports to stable branches are discussed on libc-stable,
and any patch on master that doesn't change ABI or API is
immediately suitable for backporting to a stable branch. It
is polite to post your backport to libc-stable (in parallel
with your commit) and explain the reason for the backport;
this helps distro maintainers decide if they want to sync to
get the fix.
~~~
I don't blame anyone for not finding it or knowing it, please always
feel free to ask such questions.
--
Cheers,
Carlos.