From: Alan Modra <amodra@bigpond.net.au>
To: Brian Ford <ford@vss.fsi.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Support DWARF 2/3 on i?86 PE
Date: Fri, 16 Apr 2004 04:22:00 -0000 [thread overview]
Message-ID: <20040416041405.GE2557@bubble.modra.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0404152232140.14168@thing1-200>
On Thu, Apr 15, 2004 at 10:35:54PM -0500, Brian Ford wrote:
> http://sources.redhat.com/ml/binutils/2004-04/msg00169.html
This patch is OK for mainline, provided you fix the comment formatting.
Hmm, actually the comment is wrong. You want:
/* The first non-zero section filepos is the header size.
Sections without contents will have a filepos of 0. */
> http://sources.redhat.com/ml/binutils/2004-03/msg00542.html
This is also OK.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2004-04-16 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 3:36 Brian Ford
[not found] ` <20040416033107.GD2557@bubble.modra.org>
2004-04-16 4:14 ` Brian Ford
2004-04-16 4:22 ` Alan Modra [this message]
2004-04-16 15:29 ` Brian Ford
2004-04-17 11:29 ` Alan Modra
2004-04-29 16:07 Nick Clifton
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=20040416041405.GE2557@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=ford@vss.fsi.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).