From: amodra@bigpond.net.au
To: DJ Delorie <dj@delorie.com>
Cc: nwourms@myrealbox.com, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: parallel builds failing in bfd
Date: Thu, 29 May 2003 20:37:00 -0000 [thread overview]
Message-ID: <20030529203659.GA26242@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <200305282359.h4SNx5hN009454@envy.delorie.com>
On Wed, May 28, 2003 at 07:59:05PM -0400, DJ Delorie wrote:
> Nate), and any further work is probably also going to have to wait for
> someone to volunteers to do it.
Various people have volunteered to do the work in the past, eg. see
http://sources.redhat.com/ml/binutils/2003-01/msg00143.html
It's more a matter of having _maintainers_ volunteer the time to
review and/or be willing to risk committing a patch that will likely
have some initial faults.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2003-05-29 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 22:01 David Carlton
2003-05-28 22:06 ` Daniel Jacobowitz
2003-05-28 22:51 ` Nicholas Wourms
2003-05-28 23:59 ` DJ Delorie
2003-05-29 20:37 ` amodra [this message]
2003-05-30 5:37 ` unsubsribe Gitesh Kulkarni
2003-05-29 13:51 ` parallel builds failing in bfd H. J. Lu
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=20030529203659.GA26242@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=dj@delorie.com \
--cc=gdb@sources.redhat.com \
--cc=nwourms@myrealbox.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).