From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Kevin Kirspel <kevin-kirspel@idexx.com>, newlib@sourceware.org
Subject: Re: [PATCH v2] For RTEMS-LIBBSD support, add bitcount routines
Date: Mon, 22 May 2017 06:39:00 -0000 [thread overview]
Message-ID: <59228787.2090303@embedded-brains.de> (raw)
In-Reply-To: <591E87A5.3010608@embedded-brains.de>
I will send an alternative version today since there are some cyclic
dependency problems with this definition location.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
prev parent reply other threads:[~2017-05-22 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 13:06 Kevin Kirspel
2017-05-19 5:52 ` Sebastian Huber
2017-05-22 6:39 ` Sebastian Huber [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=59228787.2090303@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=kevin-kirspel@idexx.com \
--cc=newlib@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).