From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: gti-tac@lists.linuxfoundation.org,
Khahil White <kwhite@linuxfoundation.org>
Subject: Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.
Date: Wed, 12 Apr 2023 16:46:12 -0400 [thread overview]
Message-ID: <20230412-renderer-muzzle-fb5ea0@meerkat> (raw)
In-Reply-To: <13b3266b-a410-77fd-5dfc-4e4994b630cd@redhat.com>
On Mon, Apr 03, 2023 at 01:24:21PM -0400, Carlos O'Donell wrote:
> Konstantin,
>
> The GTI TAC met on 2023-03-08 (please ignore the date typo 06-08):
> https://lore.kernel.org/gti-tac/b72a0c4f-fed3-7418-e9d6-7a277bf37b3e@redhat.com/
>
> There was consensus that we should start working through the process steps one
> project at a time and pipe-clean the process and learn as we go.
>
> I volunteered glibc as the first project because I know the most about the project
> and the requirements.
>
> I am providing the full list of glibc services for review and pricing by LF IT.
Carlos:
I'm not ignoring you, it just so happened that the ice storm (and the
subsequent loss of power) + Easter holidays basically ate away a whole week of
my productive time. I'll be responding to your email shortly, apologies for
the delay.
-K
next prev parent reply other threads:[~2023-04-12 20:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:24 Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration Carlos O'Donell
2023-04-12 20:46 ` Konstantin Ryabitsev [this message]
2023-04-12 21:28 ` Brian Behlendorf
2023-05-19 21:00 ` Konstantin Ryabitsev
2023-05-22 14:37 ` Ian Kelling
2023-05-24 20:50 ` Carlos O'Donell
2023-05-24 21:53 ` Ian Kelling
2023-05-25 11:02 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 22:47 Joseph Myers
2023-05-22 10:11 ` Joel Brobecker
2023-05-24 12:44 ` Carlos O'Donell
2023-05-24 13:43 ` Siddhesh Poyarekar
2023-05-24 14:12 ` Carlos O'Donell
2023-05-24 15:18 ` Siddhesh Poyarekar
2023-05-23 17:38 ` Konstantin Ryabitsev
2023-05-23 19:34 ` Joseph Myers
2023-05-23 19:52 ` Konstantin Ryabitsev
2023-05-23 20:12 ` Joseph Myers
2023-05-23 20:21 ` Konstantin Ryabitsev
2023-05-23 22:12 ` Joseph Myers
2023-05-24 16:29 ` Konstantin Ryabitsev
2023-05-24 18:13 ` Siddhesh Poyarekar
2023-05-24 18:55 ` Brian Behlendorf
2023-05-24 21:27 ` Siddhesh Poyarekar
2023-05-25 11:06 ` Carlos O'Donell
2023-05-24 19:06 ` Konstantin Ryabitsev
2023-05-24 19:42 ` Joseph Myers
2023-05-24 21:12 ` Siddhesh Poyarekar
2023-05-25 11:12 ` Carlos O'Donell
2023-05-24 18:58 ` Joseph Myers
2023-05-24 12:11 ` Siddhesh Poyarekar
2023-05-24 18:44 ` Joseph Myers
2023-05-24 19:58 ` Carlos O'Donell
2023-05-24 12:57 ` Carlos O'Donell
2023-05-24 18:46 ` Joseph Myers
2023-05-24 20:19 ` Carlos O'Donell
2023-05-24 20:48 ` Joseph Myers
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=20230412-renderer-muzzle-fb5ea0@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.org \
--cc=kwhite@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.