From: Ben Elliston <bje@au1.ibm.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org, ian@airs.com,
dberlin@dberlin.org
Subject: Re: PATCH: remove libiberty/ternary.c et al
Date: Wed, 25 Jul 2007 02:08:00 -0000 [thread overview]
Message-ID: <1185328845.14525.1.camel@localhost> (raw)
In-Reply-To: <200707250140.l6P1eVjQ002759@greed.delorie.com>
On Tue, 2007-07-24 at 21:40 -0400, DJ Delorie wrote:
> It's been sitting there for six years, and I'm not a fan of making new
> libiberty versions not backward compatible. Are there any other
> reasons to remove it besides "it's there" ?
Only the burden of maintaining it.
There is only a backward compatibility problem if there is a client of
these routines and we have no reason to believe there is.
Ben
next prev parent reply other threads:[~2007-07-25 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 1:40 Ben Elliston
2007-07-25 2:00 ` DJ Delorie
2007-07-25 2:08 ` Ben Elliston [this message]
2007-07-25 3:58 ` DJ Delorie
2007-07-25 5:21 ` Daniel Berlin
2007-07-25 6:39 ` Ian Lance Taylor
2007-07-25 15:25 ` Ben Elliston
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=1185328845.14525.1.camel@localhost \
--to=bje@au1.ibm.com \
--cc=binutils@sourceware.org \
--cc=dberlin@dberlin.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ian@airs.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