From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: possible bug in bfd/sunos.c
Date: Tue, 28 May 1996 12:14:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.91.960528140102.13030X-100000@merlin> (raw)
In-Reply-To: <199605281607.MAA13904@sanguine.cygnus.com>
Thanks for the tip. Adding the third condition to the assert in question
fixed the problem. Now I get the undefined message I did not even know
to expect. :)
--joel
prev parent reply other threads:[~1996-05-28 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-28 8:56 Joel Sherrill
1996-05-28 9:07 ` Ian Lance Taylor
1996-05-28 12:14 ` Joel Sherrill [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=Pine.SV4.3.91.960528140102.13030X-100000@merlin \
--to=joel@merlin.gcs.redstone.army.mil \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.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).