From: Samuel Thibault <samuel.thibault@gnu.org>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: libc-alpha@sourceware.org, bug-hurd@gnu.org
Subject: Re: [PATCH 0/1] Let's improve/fix ccty handling
Date: Sat, 15 Apr 2023 19:58:26 +0200 [thread overview]
Message-ID: <20230415175826.at5pjnu2wp54vlhv@begin> (raw)
In-Reply-To: <20230415161718.80668-1-bugaevc@gmail.com>
Sergey Bugaev, le sam. 15 avril 2023 19:17:17 +0300, a ecrit:
> Do I understand it right that this hooks system is libc-internal? --
> or can user programs add their own functions to the hooks?
I don't think it was meant to be used by user programs.
Samuel
next prev parent reply other threads:[~2023-04-15 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 16:17 Sergey Bugaev
2023-04-15 16:17 ` [PATCH 1/1] hurd: Avoid extra ctty RPCs in init_dtable () Sergey Bugaev
2023-04-17 12:08 ` Samuel Thibault
2023-04-15 17:58 ` Samuel Thibault [this message]
2023-04-15 19:08 ` [PATCH] hurd: Run init_pids () before " Sergey Bugaev
2023-04-17 21:05 ` Samuel Thibault
2023-04-17 12:14 ` [PATCH 0/1] Let's improve/fix ccty handling Samuel Thibault
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=20230415175826.at5pjnu2wp54vlhv@begin \
--to=samuel.thibault@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=bugaevc@gmail.com \
--cc=libc-alpha@sourceware.org \
/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).