From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH] local.conf.sample: disable prelink
Date: Tue, 15 Jun 2021 10:55:51 +0200 [thread overview]
Message-ID: <CANNYZj84MXS57sG5CWLmS-Y_0-w8h1_9NLmtjFEo4pJ5snXvcA@mail.gmail.com> (raw)
In-Reply-To: <5ed9e1d2676d4d31289ebaf2ec3b492c1daa88a7.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
On Tue, 15 Jun 2021 at 10:48, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> I appreciate the desire simply to delete/disable anything that causes
> issues
> but in this case I draw the line and my answer is no. It works fine in the
> vast majority of usage.
>
But where are the benchmarks that show it's actually beneficial? And
commitment from someone to maintain it and address open issues (there are
more than just this one)?
Alex
[-- Attachment #2: Type: text/html, Size: 832 bytes --]
next prev parent reply other threads:[~2021-06-15 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 8:12 [PATCH] local.conf.sample: disable prelink Alexander Kanavin
2021-06-15 8:48 ` [poky] " Richard Purdie
2021-06-15 8:55 ` Alexander Kanavin [this message]
2021-06-15 9:04 ` Richard Purdie
2021-06-15 15:21 ` Alexander Kanavin
2021-06-15 17:38 ` [yocto] " Khem Raj
2021-06-16 9:11 ` Richard Purdie
2021-06-16 9:45 ` Alexander Kanavin
2021-07-19 20:58 ` [yocto] " Robert Berger
2021-07-22 19:05 ` Alexander Kanavin
2021-07-23 12:51 ` Robert Berger
2021-06-15 17:21 ` Khem Raj
2021-07-05 18:36 Alexander Kanavin
2021-07-05 23:06 ` [poky] " Khem Raj
2021-07-06 0:03 ` Armin Kuster
2021-07-06 7:36 ` Alexander Kanavin
2021-07-06 8:34 ` Khem Raj
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=CANNYZj84MXS57sG5CWLmS-Y_0-w8h1_9NLmtjFEo4pJ5snXvcA@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=poky@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.