From: Andreas Schwab <schwab@suse.de>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Andrew STUBBS <andrew.stubbs@st.com>, binutils@sources.redhat.com
Subject: Re: Problem setting the CONTENTS flag
Date: Fri, 21 Apr 2006 23:32:00 -0000 [thread overview]
Message-ID: <jeslo7t1um.fsf@sykes.suse.de> (raw)
In-Reply-To: <20060421143558.GA13559@lucon.org> (H. J. Lu's message of "Fri, 21 Apr 2006 07:35:58 -0700")
"H. J. Lu" <hjl@lucon.org> writes:
> + /* When we read a file or section BFD flags has been set, we don't
s/has/have/
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-04-21 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 18:08 Andrew STUBBS
2006-04-21 22:26 ` H. J. Lu
2006-04-21 23:32 ` Andreas Schwab [this message]
2006-04-23 22:13 ` H. J. Lu
2006-04-24 19:55 ` Andrew STUBBS
2006-04-25 16:37 ` Nick Clifton
2006-04-26 0:21 ` PATCH: binutils/2593: " H. J. Lu
2006-04-26 12:16 ` Nick Clifton
2006-04-26 0:39 ` H. J. Lu
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=jeslo7t1um.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=andrew.stubbs@st.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.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).