From: Andrew Haley <aph@redhat.com>
To: Tom Tromey <tom@tromey.com>,
"Kaz Kylheku (libffi)" <382-725-6798@kylheku.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: Cosure return value issue on Linux PPC64
Date: Mon, 29 May 2017 15:30:00 -0000 [thread overview]
Message-ID: <7d4ea836-9d86-884b-2315-d0055f050da8@redhat.com> (raw)
In-Reply-To: <8737bnetf4.fsf@bapiya>
On 29/05/17 13:31, Tom Tromey wrote:
> I hope this helps, but if it's still insufficiently clear, I'd
> appreciate suggestions for how to improve it.
A couple of examples would help. I find that wordage confusing.
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
prev parent reply other threads:[~2017-05-29 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 16:59 Kaz Kylheku (libffi)
2017-05-29 7:44 ` Andrew Haley
2017-05-29 12:31 ` Tom Tromey
2017-05-29 15:30 ` Andrew Haley [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=7d4ea836-9d86-884b-2315-d0055f050da8@redhat.com \
--to=aph@redhat.com \
--cc=382-725-6798@kylheku.com \
--cc=libffi-discuss@sourceware.org \
--cc=tom@tromey.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).