From: Andreas Schwab <schwab@suse.de>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, arnaud.lb@gmail.com
Subject: Re: [PATCH v2] stdio: Do not ignore posix_spawn error on popen (BZ #29016)
Date: Tue, 14 Feb 2023 16:13:38 +0100 [thread overview]
Message-ID: <mvmilg4th3x.fsf@suse.de> (raw)
In-Reply-To: <1cfa9229-9edd-82e3-42b2-a60c9798c69a@linaro.org> (Adhemerval Zanella Netto's message of "Thu, 9 Feb 2023 16:43:02 -0300")
I've already ok'd it 9 weeks ago.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-02-14 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 18:24 Adhemerval Zanella
2023-01-10 15:21 ` Adhemerval Zanella Netto
2023-02-09 19:43 ` Adhemerval Zanella Netto
2023-02-14 15:13 ` Andreas Schwab [this message]
2023-02-14 16:54 ` Adhemerval Zanella Netto
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=mvmilg4th3x.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=arnaud.lb@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).