From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [glibc] posix: Add terminal control setting support for posix_spawn
Date: Thu, 27 Jan 2022 13:15:13 +0100 [thread overview]
Message-ID: <8735l9nzn2.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <080dfb07-9a33-4cd2-e745-1e49c99624b4@linaro.org> (Adhemerval Zanella's message of "Thu, 27 Jan 2022 09:02:11 -0300")
* Adhemerval Zanella:
>>> posix_spawn_file_actions_t actions;
>>> posix_spawn_file_actions_init (&actions);
>>> posix_spawn_file_actions_tcsetgrp_np (&actions, tcfd);
>
> In fact I think it should be posix_spawn_file_actions_addtcsetgrp_np
> to follow other file action naming convention.
Yes, that name is better.
Thanks,
Florian
prev parent reply other threads:[~2022-01-27 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220125180124.B88AC3857C70@sourceware.org>
2022-01-27 10:49 ` Florian Weimer
2022-01-27 11:38 ` Adhemerval Zanella
2022-01-27 11:57 ` Florian Weimer
2022-01-27 12:02 ` Adhemerval Zanella
2022-01-27 12:15 ` Florian Weimer [this message]
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=8735l9nzn2.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--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).