From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [ob] Rename NO_ERROR
Date: Sat, 04 Feb 2006 12:00:00 -0000 [thread overview]
Message-ID: <u4q3fnxkq.fsf@gnu.org> (raw)
In-Reply-To: <20060203215146.GA3349@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 3 Feb 2006 16:51:46 -0500)
> Date: Fri, 3 Feb 2006 16:51:46 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> The Windows (at least mingw32's version) headers apparently define NO_ERROR.
> The least of several cretinous things I've learned about Windows programming
> in the last week.
Out of curiosity, what were the other cretinous things? (Mail me
privately if you think the answer will not be interesting to others.)
next prev parent reply other threads:[~2006-02-04 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 21:51 Daniel Jacobowitz
2006-02-04 12:00 ` Eli Zaretskii [this message]
2006-02-04 15:14 ` Daniel Jacobowitz
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=u4q3fnxkq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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