From: Sergey Bugaev <bugaevc@gmail.com>
To: Flavio Cruz <flaviocruz@gmail.com>
Cc: bug-hurd <bug-hurd@gnu.org>,
libc-alpha@sourceware.org,
Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: [PATCH glibc] Stop checking if MiG supports retcode.
Date: Wed, 10 May 2023 08:36:41 +0300 [thread overview]
Message-ID: <CAN9u=HfUw2-6b2Ac4sCG8OhLKBdHVD9b3OsVOQHmVKkRJdquCw@mail.gmail.com> (raw)
In-Reply-To: <ZFspor91aoMwbh9T@jupiter.tail36e24.ts.net>
Hello,
On Wed, May 10, 2023, 08:21 Flavio Cruz <flaviocruz@gmail.com> wrote:
> HAVE_MIG_RETCODE is removed completely since this will be a no-op either
> way (compiling against old Hurd headers will work the same, new Hurd
> headers will result in the same stubs since retcode is a no-op).
It is a no-op currently, but please note that I was planning to make
it not a no-op some time (I wanted my epoll server to return error
replies properly). Will that cause any issues?
Sergey
next prev parent reply other threads:[~2023-05-10 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 5:20 Flavio Cruz
2023-05-10 5:36 ` Sergey Bugaev [this message]
2023-05-15 4:09 ` Flávio Cruz
2023-05-10 23:28 ` 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='CAN9u=HfUw2-6b2Ac4sCG8OhLKBdHVD9b3OsVOQHmVKkRJdquCw@mail.gmail.com' \
--to=bugaevc@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=flaviocruz@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@gnu.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).