From: Ben Elliston <bje@wasabisystems.com>
To: binutils@sources.redhat.com
Subject: Re: The Linux binutils 2.14.90.0.1 is released
Date: Fri, 09 May 2003 07:24:00 -0000 [thread overview]
Message-ID: <87fznor392.fsf@sashimi.wasabisystems.com> (raw)
In-Reply-To: <20030505223301.A28436@lucon.org>
Hi HJ,
"H. J. Lu" <hjl@lucon.org> writes:
> This is the beta release of binutils 2.14.90.0.1 for Linux, which is
> based on binutils 2003 0505 in CVS on sourecs.redhat.com plus
> various changes. It is purely for Linux.
As I understand it, you started up your "HJ special" binutils around
the time that binutils development has slowed/stalled. It is now
actively maintained. I'm left wondering why it is necessary for you
to continue to maintain your own binutils releases. Can your changes
be folded into mainline binutils?
Ben
next prev parent reply other threads:[~2003-05-09 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030505223301.A28436@lucon.org>
[not found] ` <hod6iwy26e.fsf@byrd.suse.de>
2003-05-06 15:41 ` PATCH: Don't use empy files in ld-elfvers H. J. Lu
2003-05-09 7:24 ` Ben Elliston [this message]
2003-05-09 13:04 The Linux binutils 2.14.90.0.1 is released Jack Howarth
2003-05-09 14:51 ` H. J. Lu
2003-05-10 0:17 ` Ben Elliston
2003-05-10 14:36 ` Thiemo Seufer
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=87fznor392.fsf@sashimi.wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=binutils@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).