public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Evaluating a new malloc()
Date: Tue, 26 Feb 2013 18:07:46 -0600	[thread overview]
Message-ID: <20130227000746.GA31311@linux1> (raw)
In-Reply-To: <CAEdQ38F_bD7vTNw3T5WouBCNEeLYo1azFsj7KEBrEnkmCOSqVw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

On Tue, Feb 26, 2013 at 11:10:09AM -0800, Matt Turner wrote:
> On Tue, Feb 26, 2013 at 8:35 AM, Alec Warner <antarus@gentoo.org> wrote:
> > In terms of 'following Gentoo policy.' We encourage packages to be as
> > close to upstream as possible. I cannot fathom why when you basically
> > find a performance bug in malloc, you start a thread on the list about
> > replacing it; as opposed to filing a bug against glibc or emailing the
> > glibc lists and asking them about it.
> 
> We may not understand it, but it does completely fit ryao's typical
> modus operandi.

I must second this unfortunately.

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-02-27  0:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 13:33 [gentoo-dev] Evaluating a new malloc() Richard Yao
2013-02-26 13:35 ` Diego Elio Pettenò
2013-02-26 13:46   ` Richard Yao
2013-02-26 13:48 ` Alexander Berntsen
2013-02-26 13:52   ` Richard Yao
2013-02-26 14:25     ` Florian Philipp
2013-02-26 16:35 ` Alec Warner
2013-02-26 16:44   ` Rich Freeman
2013-02-26 21:37     ` Maciej Mrozowski
2013-02-26 21:49       ` Jeff Horelick
2013-02-26 22:08       ` Matt Turner
2013-03-19 21:08     ` Mike Frysinger
2013-02-26 19:10   ` Matt Turner
2013-02-27  0:07     ` William Hubbs [this message]
2013-02-26 16:40 ` Mike Gilbert
2013-02-27  5:22 ` [gentoo-dev] " Ryan Hill
2013-02-27 16:15   ` Peter Stuge
2013-02-27 20:26 ` [gentoo-dev] " Sergei Trofimovich

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=20130227000746.GA31311@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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