From: Alan Modra <amodra@gmail.com>
To: Doug Evans <dje@google.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Add typedefs for bfd_openr_iovec functions
Date: Thu, 07 Aug 2014 08:17:00 -0000 [thread overview]
Message-ID: <20140807081745.GZ8921@bubble.grove.modra.org> (raw)
In-Reply-To: <yjt2oavyj2i9.fsf@ruffy.mtv.corp.google.com>
On Tue, Aug 05, 2014 at 09:59:58AM -0700, Doug Evans wrote:
> - I put the CODE_FRAGMENT in its own comment, not sure whether there
> were any conventions to do otherwise. Let me know if/how you'd like
> this done differently.
Putting the typedefs in a CODE_FRAGMENT doesn't look very nice in
opncls.texi or bfd.info. I believe they would be best placed in the
synopsis of bfd_openr_iovec, and without comments.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2014-08-07 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 17:00 Doug Evans
2014-08-07 8:17 ` Alan Modra [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=20140807081745.GZ8921@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=dje@google.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).