From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: pthread_getname_np implementation
Date: Fri, 21 Jun 2019 10:04:59 -0400 [thread overview]
Message-ID: <20190621140459.GW1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <AM0PR07MB442007DDD4FECFF99BB5EBF48BE70@AM0PR07MB4420.eurprd07.prod.outlook.com>
On Fri, Jun 21, 2019 at 01:36:49PM +0000, Poggiali, Antonio wrote:
> Hello,
>
> I've written the missing API pthread_getname_np for the latest version of the library.
> In attachment the patch to apply in on the master branch.
>
> I'd really like to see it integrated in the next release.
I think this was brought up before and it was deemed not appropriate
for inclusion because there are multiple incompatible historical
functions by the same name. I'll see what I can find from past
discussions.
Rich
next prev parent reply other threads:[~2019-06-21 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 13:36 Poggiali, Antonio
2019-06-21 14:04 ` Rich Felker [this message]
2019-06-21 18:18 ` Rich Felker
2019-07-03 7:31 Poggiali, Antonio
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=20190621140459.GW1506@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).