From: fche@redhat.com (Frank Ch. Eigler)
To: Sam James <sam@gentoo.org>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Paul Eggert <eggert@cs.ucla.edu>,
Mark Wielaard <mark@klomp.org>,
Jakub Jelinek <jakub@redhat.com>,
libc-alpha@sourceware.org, Andreas Schwab <schwab@suse.de>,
Joseph Myers <joseph@codesourcery.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Fri, 01 Sep 2023 12:19:54 -0400 [thread overview]
Message-ID: <875y4tuaqd.fsf@redhat.com> (raw)
In-Reply-To: <87sf7yc4py.fsf@gentoo.org> (Sam James's message of "Fri, 01 Sep 2023 16:01:02 +0100")
sam wrote:
> [...] I can see the advantage in dedicated devops and service
> isolation - although I don't know if sw has given an opinion on
> whether they can do service isolation. [...]
For what it's worth, I don't recall seeing an actual complete worked-out
plan for precisely what kinds of isolation are desired (never mind why),
and how they would all be provided at LF. Therefore, it has not been
possible for sourceware folks to contemplate providing an equivalent.
- FChE
next prev parent reply other threads:[~2023-09-01 16:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` Alexandre Oliva
2023-08-30 17:31 ` Joseph Myers
2023-08-31 19:59 ` Paul Eggert
2023-09-01 6:03 ` Sam James
2023-09-01 8:55 ` Florian Weimer
2023-09-01 9:02 ` Sam James
2023-09-01 9:21 ` dmarc, dkim and From rewriting Mark Wielaard
2023-09-01 11:52 ` Florian Weimer
2023-09-01 9:03 ` [Action Required] glibc decision to use CTI services Andrew Pinski
2023-09-01 11:49 ` Florian Weimer
2023-09-01 13:32 ` Frank Ch. Eigler
2023-09-01 12:30 ` Siddhesh Poyarekar
2023-09-01 14:54 ` Paul Eggert
2023-09-01 16:08 ` Siddhesh Poyarekar
2023-09-01 15:01 ` Sam James
2023-09-01 16:19 ` Frank Ch. Eigler [this message]
2023-09-01 16:30 ` Siddhesh Poyarekar
2023-09-02 18:25 ` Mark Wielaard
2023-09-01 9:08 ` Mark Wielaard
2023-09-03 6:31 ` Alexandre Oliva
2023-09-27 13:49 ` Carlos O'Donell
2023-10-04 0:09 ` Paul Eggert
2023-09-01 15:09 ` Alexandre Oliva
2023-09-27 13:50 ` Carlos O'Donell
2024-02-13 0:43 ` Carlos O'Donell
2024-02-19 21:22 ` Alexandre Oliva
2024-02-19 22:03 ` DJ Delorie
2024-02-20 1:49 ` Mark Wielaard
2024-02-20 3:01 ` Alexandre Oliva
2023-08-31 8:37 ` Mark Wielaard
2023-09-01 15:08 ` Alexandre Oliva
2023-08-31 10:34 ` Florian Weimer
2023-09-04 6:09 ` Alexandre Oliva
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=875y4tuaqd.fsf@redhat.com \
--to=fche@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.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).