From: DJ Delorie <dj@redhat.com>
To: JBeulich@novell.com
Cc: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com
Subject: Re: libiberty addition (for binutils): unlink_if_ordinary
Date: Tue, 22 Feb 2005 18:36:00 -0000 [thread overview]
Message-ID: <200502221445.j1MEjChn006114@greed.delorie.com> (raw)
In-Reply-To: <s21b15e2.073@emea1-mh.id2.novell.com> (JBeulich@novell.com)
> But the patch is to libiberty, not gcc.
libiberty is part of gcc. The other projects share gcc's copy.
> And it doesn't seem logical to throttle other projects because of
> the current mainline state of gcc...
Would you rather I break gcc just before a release?
next parent reply other threads:[~2005-02-22 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s21b15e2.073@emea1-mh.id2.novell.com>
2005-02-22 18:36 ` DJ Delorie [this message]
2005-03-02 8:46 Jan Beulich
[not found] <s1f74c78.013@emea1-mh.id2.novell.com>
2005-03-01 1:32 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 18:29 Jan Beulich
[not found] <s21a0df3.067@emea1-mh.id2.novell.com>
2005-02-21 21:50 ` DJ Delorie
2005-02-21 19:45 Jan Beulich
2005-01-26 7:53 Jan Beulich
2005-03-02 0:12 ` Hans-Peter Nilsson
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=200502221445.j1MEjChn006114@greed.delorie.com \
--to=dj@redhat.com \
--cc=JBeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/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).