From: Andrew Cagney <ac131313@redhat.com>
To: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: [patch] "struct symbol_cache_entry" -> "struct bfd_symbol"
Date: Mon, 27 Oct 2003 17:03:00 -0000 [thread overview]
Message-ID: <3F9D4FE0.8030209@redhat.com> (raw)
Hello,
Per an earlier post and thumbs up, I'm planning on making the rename:
"struct symbol_cache_entry" -> "struct bfd_symbol"
at roughly 2003-10-31 0500 UTC (roughly midnight Thursday US East coast
time) (and assuming that my internet is up this time ...).
I'll post the real patch once its done.
Andrew
next reply other threads:[~2003-10-27 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 17:03 Andrew Cagney [this message]
2003-10-31 5:26 ` Andrew Cagney
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=3F9D4FE0.8030209@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.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