From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: [APPROVE?] GNU linkonce patch
Date: Wed, 09 Apr 2003 19:05:00 -0000 [thread overview]
Message-ID: <3E946EF6.7060704@eCosCentric.com> (raw)
I just sent a fix for an obvious typo in various linker scripts to
ecos-patches. A number of .ld files had .gnulinkonce.s instead of
.gnu.linkonce.s.
http://sources.redhat.com/ml/ecos-patches/2003-04/msg00057.html
It should be applied because a) it's obvious and b) without it people on
quite a few targets may not have working new/delete. The risks are zero
unless I had a finger fumble!
Please someone say yes so I don't have to hang around worrying about
whether I'll forget to apply it! :-)
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next reply other threads:[~2003-04-09 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 19:05 Jonathan Larmour [this message]
2003-04-09 21:21 ` Gary Thomas
2003-04-12 4:47 ` Jonathan Larmour
2003-04-14 12:01 ` Nick Garnett
2003-04-14 12:21 ` Jonathan Larmour
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=3E946EF6.7060704@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).