From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001986] Make select FD_COPY and FD_ZERO macros single statements
Date: Mon, 16 Jun 2014 10:07:00 -0000 [thread overview]
Message-ID: <bug-1001986-104-vQsIlAaLLM@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001986-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001986
John Dallaway <john@dallaway.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |john@dallaway.org.uk
Resolution|--- |CURRENTRELEASE
Assignee|unassigned@bugs.ecos.source |john@dallaway.org.uk
|ware.org |
--- Comment #1 from John Dallaway <john@dallaway.org.uk> ---
Andy, thank you for contributing. Fix checked-in.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-16 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 13:44 [Bug 1001986] New: " bugzilla-daemon
2014-06-16 10:07 ` bugzilla-daemon [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=bug-1001986-104-vQsIlAaLLM@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.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).