From: Corinna Vinschen <vinschen@redhat.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: newlib@sourceware.org
Subject: Re: [PATCH v3 1/3] Fix RTEMS CPU_EQUAL_S()
Date: Wed, 07 Jun 2017 13:02:00 -0000 [thread overview]
Message-ID: <20170607130256.GA15217@calimero.vinschen.de> (raw)
In-Reply-To: <71f45b57-72c6-3f33-f565-02caa0d06701@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
On Jun 7 09:35, Sebastian Huber wrote:
> I am really sorry for needing four attempts to get this right.
No worries. Please apply.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-06-07 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 7:34 Sebastian Huber
2017-06-07 7:34 ` [PATCH v3 2/3] Fix some RTEMS CPUSET(9) macros Sebastian Huber
2017-06-07 7:34 ` [PATCH v3 3/3] Update FreeBSD revision of RTEMS <sys/bitset.h> Sebastian Huber
2017-06-07 7:35 ` [PATCH v3 1/3] Fix RTEMS CPU_EQUAL_S() Sebastian Huber
2017-06-07 13:02 ` 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=20170607130256.GA15217@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).