From: Carlos O'Donell <carlos@redhat.com>
To: gti-tac@lists.linuxfoundation.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Khahil White <kwhite@linuxfoundation.org>
Subject: Re: Size of bread box analysis for gcc, binutils, gdb and glibc total migration.
Date: Mon, 3 Apr 2023 16:11:56 -0400 [thread overview]
Message-ID: <55958c9d-7395-3d45-b3e0-5290936fca7e@redhat.com> (raw)
In-Reply-To: <74d44891-f436-f949-0efa-bca9b1351ecf@redhat.com>
On 4/3/23 14:04, Carlos O'Donell wrote:
> Konstantin,
>
> I would like to also update the current "size of the IT bread box" analysis
> for gcc, binutils, gdb and glibc as a total cost for CY23. This will help
> the OpenSSF plan for backstopping the cost.
>
> GCC service enumeration:
> https://lore.kernel.org/gti-tac/7e59d8db-7b26-1249-ad5c-67b7f3411e1@codesourcery.com/T/#u
>
> GLIBC service enumeration:
> https://lore.kernel.org/gti-tac/13b3266b-a410-77fd-5dfc-4e4994b630cd@redhat.com/T/#u
>
> BINUTILS service enumeration:
> https://lore.kernel.org/gti-tac/679ba29a-24c7-6684-a565-0e5d5db05b19@redhat.com/
>
> GDB service enumeration:
> https://lore.kernel.org/gti-tac/b755774c-3912-2dac-957c-91f659c95119@efficios.com/
>
> Please send such an updated "size of the bread box" to Brian Behlendorf
> at the OpenSSF and Khahil White (on TO:).
My apologies Konstantin, this email was way more curt than I intended to write.
Let me restart this by saying "May you please also have a look at the following for us..." :-)
I appreciate LF IT's help in all of these evaluations, and I know it takes quite
a bit of time to review the details and the exact requirements.
--
Cheers,
Carlos.
prev parent reply other threads:[~2023-04-03 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:04 Size of bread box analysis for gcc, binutils, gdb and glibc total migration Carlos O'Donell
2023-04-03 20:11 ` Carlos O'Donell [this message]
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=55958c9d-7395-3d45-b3e0-5290936fca7e@redhat.com \
--to=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.org \
--cc=konstantin@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 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).