From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <codonell@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: RFC: test-in-container vs ld.so
Date: Tue, 10 Dec 2019 14:37:02 -0500 [thread overview]
Message-ID: <xnlfrkt1k1.fsf@greed.delorie.com> (raw)
In-Reply-To: <e5bd7df9-48e8-88b7-a2a0-6da388c6b7e0@redhat.com> (codonell@redhat.com)
"Carlos O'Donell" <codonell@redhat.com> writes:
>> So, we're already not running ld.so in the container anyway :-P
>
> Yay! Does that mean we don't have a bug?
I think we should still adjust the Makefiles so that what the user sees
in the logs more accurately reflects reality.
next prev parent reply other threads:[~2019-12-10 19:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 22:31 RFC: test-in-container vs ld.so DJ Delorie
2019-11-08 7:27 ` Florian Weimer
2019-11-08 8:05 ` DJ Delorie
2019-11-08 8:25 ` Florian Weimer
2019-11-08 23:54 ` DJ Delorie
2019-11-09 13:24 ` Carlos O'Donell
2019-11-09 14:05 ` Florian Weimer
2019-12-06 4:19 ` DJ Delorie
2019-12-06 20:09 ` DJ Delorie
2019-12-10 19:33 ` Carlos O'Donell
2019-12-10 19:37 ` DJ Delorie [this message]
2019-11-08 15:07 ` Carlos O'Donell
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xnlfrkt1k1.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=codonell@redhat.com \
--cc=libc-alpha@sourceware.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).