From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Map ERROR_NO_SUCH_DEVICE and ERROR_MEDIA_CHANGED to ENODEV
Date: Mon, 26 Feb 2024 12:36:10 +0100 [thread overview]
Message-ID: <Zdx3qtxjpH-7Y4Py@calimero.vinschen.de> (raw)
In-Reply-To: <d22da40f-ea54-096a-75ea-28a236125cf4@t-online.de>
On Feb 26 12:14, Christian Franke wrote:
> Corinna Vinschen wrote:
> > Why so many? I used winerror.h to populate the list not too long ago,
> > so I wonder why it suddenly has so many more error codes?
>
> "Required for mozilla-central." - 850 insertions:
> https://sourceforge.net/p/mingw-w64/mingw-w64/ci/ddeb05a
>
> Most or all would possible never occur with the NTDLL/Win32 API subset used
> by Cygwin.
>
> Includes interesting codes like "ERROR_NO_WORK_DONE" :-)
LOL. The only hint I found on that one is in Wine ChangeLog:
"FormatMessage() now reports ERROR_NO_WORK_DONE error for empty string."
Corinna
prev parent reply other threads:[~2024-02-26 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 18:14 Christian Franke
2024-02-24 12:21 ` Corinna Vinschen
2024-02-25 9:12 ` Christian Franke
2024-02-26 10:27 ` Corinna Vinschen
2024-02-26 11:14 ` Christian Franke
2024-02-26 11:36 ` Corinna Vinschen [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=Zdx3qtxjpH-7Y4Py@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.com \
/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).