From: Nick Clifton <nickc@redhat.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: binutils@sources.redhat.com, Ben Elliston <bje@au1.ibm.com>
Subject: Re: PATCH: speed up ar(1)
Date: Mon, 14 Mar 2005 09:40:00 -0000 [thread overview]
Message-ID: <42355F0A.9020502@redhat.com> (raw)
In-Reply-To: <200503140205.47682.stevenb@suse.de>
Hi Steven,
>>Approved for the mainline, but not the 2.16 branch.
> Ouch, that's a shame.
You can try to persuade Daniel that including it in the branch would be
a good idea, but I doubt if he would agree. The problem is that the
patch is too new and has the potential to introduce sublte new bugs
which are not immediealtey obvious from reviewing the code. I would
rather that the 2.16 branch produce a working-but-slow ar than a
fast-but-broken one.
Cheers
Nick
next prev parent reply other threads:[~2005-03-14 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 23:47 Ben Elliston
2005-03-09 12:41 ` Nick Clifton
2005-03-10 0:05 ` Ben Elliston
2005-03-14 1:06 ` Steven Bosscher
2005-03-14 1:32 ` H. J. Lu
2005-03-14 1:38 ` Alan Modra
2005-03-14 9:40 ` Nick Clifton [this message]
2005-03-14 16:24 ` Daniel Jacobowitz
2005-03-10 21:31 ` Mark Kettenis
2005-03-10 22:40 ` 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=42355F0A.9020502@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=bje@au1.ibm.com \
--cc=stevenb@suse.de \
/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).