From: Joseph Myers <joseph@codesourcery.com>
To: stsp <stsp2@yandex.ru>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/2] dlfcn,elf: implement dlmem() function [BZ #11767]
Date: Mon, 13 Feb 2023 21:46:14 +0000 [thread overview]
Message-ID: <8ca35d-efc9-498-edf8-e0f166dcd8f@codesourcery.com> (raw)
In-Reply-To: <99c1d55b-a632-ec08-1c9b-870b7409ad74@yandex.ru>
On Sun, 12 Feb 2023, stsp via Libc-alpha wrote:
> > A new function needs to be given the symbol version of the *next* release,
> > not added to Versions for an *old* release. And then all abilist files
> > need updating, not just one.
>
> Changed to 2.37, updated abifiles.
2.37 is the *last* version, not the next one; since it's been released, no
more symbols can be added to it. You need to use 2.38, not 2.37.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-02-13 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 14:07 [PATCH 1/2] elf: strdup() l_name if no realname [BZ #30100] Stas Sergeev
2023-02-10 14:07 ` [PATCH 2/2] dlfcn,elf: implement dlmem() function [BZ #11767] Stas Sergeev
2023-02-10 21:51 ` Joseph Myers
2023-02-11 20:10 ` stsp
2023-02-13 21:46 ` Joseph Myers [this message]
2023-02-14 8:42 ` stsp
2023-02-13 13:23 [PATCH v3 0/2] implement dlmem() function Stas Sergeev
2023-02-13 13:23 ` [PATCH 2/2] dlfcn,elf: implement dlmem() function [BZ #11767] Stas Sergeev
2023-02-13 13:45 ` Florian Weimer
2023-02-13 16:36 ` stsp
2023-02-14 8:43 ` stsp
2023-03-18 17:28 ` stsp
2023-02-14 8:41 [PATCH v4 0/2] implement dlmem() function Stas Sergeev
2023-02-14 8:41 ` [PATCH 2/2] dlfcn,elf: implement dlmem() function [BZ #11767] Stas Sergeev
2023-02-14 9:51 ` Florian Weimer
2023-02-14 13:13 ` stsp
2023-02-15 11:30 ` stsp
2023-03-18 16:58 ` stsp
2023-02-15 11:21 [PATCH v5 0/2] implement dlmem() with audit extension Stas Sergeev
2023-02-15 11:21 ` [PATCH 2/2] dlfcn,elf: implement dlmem() function [BZ #11767] Stas Sergeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ca35d-efc9-498-edf8-e0f166dcd8f@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=stsp2@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).