From: Ken Brown <kbrown@cornell.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: ptsname_r on Cygwin
Date: Fri, 22 Jan 2021 10:48:14 -0500 [thread overview]
Message-ID: <312479e2-ad3e-afc0-7aec-a70e54a0d6f5@cornell.edu> (raw)
In-Reply-To: <9243579b-7993-6a4d-c043-f9049e0ebbec@cornell.edu>
On 1/21/2021 5:45 PM, Ken Brown wrote:
> On 1/21/2021 3:26 PM, Bruno Haible wrote:
>> Ken Brown wrote:
>>> Thanks for the report. I've submitted a patch that fixes this:
>>>
>>> https://cygwin.com/pipermail/cygwin-patches/2021q1/010995.html
>>
>> Thanks. EBADF is the more "proper" errno value here, for fd < 0. But
>> glibc produces errno ENOTTY in this case; so it should be acceptable too.
>
> I thought EBADF made more sense too, but Cygwin generally tries to emulate
> Linux. We'll see what Corinna thinks.
Corinna agreed with you but left it up to me, so I went with EBADF.
Thanks.
Ken
prev parent reply other threads:[~2021-01-22 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 6:31 ptsname_r on Cygwin Bruno Haible
2021-01-20 8:11 ` Bruno Haible
2021-01-21 18:21 ` Ken Brown
2021-01-21 20:26 ` Bruno Haible
2021-01-21 22:45 ` Ken Brown
2021-01-22 15:48 ` Ken Brown [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=312479e2-ad3e-afc0-7aec-a70e54a0d6f5@cornell.edu \
--to=kbrown@cornell.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@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).