All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
	gti-tac@lists.linuxfoundation.org,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: Action: Setup working group for the GNU Toolchain proposal to migrate to LF IT managed services
Date: Tue, 15 Nov 2022 12:25:11 -0800	[thread overview]
Message-ID: <Y3P1p4thdlOLES9l@adacore.com> (raw)
In-Reply-To: <ce1a98c9-a512-855d-3ad2-53ae69e0847e@redhat.com>

Hi everyone,

> >> - Seek volunteers. Please respond to this email if you want to volunteer
> >>   to be on the "LF IT managed services" working group and help enumerate
> >>   services.
> > 
> > I'll volunteer to be on it, but, as noted at the meeting, I don't expect 
> > to do much on the enumeration before January.
> > 
> 
> I will also volunteer to be on it, and I can start documenting right
> away for all the services I know glibc needs.

I can help with the GDB side of things. I don't know if I know all
of them, but I know some, at least.

-- 
Joel

  reply	other threads:[~2022-11-15 20:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 17:24 Action: Setup working group for the GNU Toolchain proposal to migrate to LF IT managed services Carlos O'Donell
2022-11-11 23:36 ` Joseph Myers
2022-11-15 19:42   ` Carlos O'Donell
2022-11-15 20:25     ` Joel Brobecker [this message]
2022-11-17 14:10       ` Simon Marchi
2022-11-21  3:31 ` Joel Brobecker
2022-11-21  3:32   ` Joel Brobecker
2022-11-21 20:49   ` Joseph Myers
2022-12-05 17:45     ` David Edelsohn
2022-12-12  4:44       ` Joel Brobecker
2022-12-06 15:52     ` Simon Marchi
2022-12-06 17:42       ` Simon Marchi
2022-12-06 17:43         ` David Edelsohn
2022-12-24  5:31         ` Joel Brobecker

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=Y3P1p4thdlOLES9l@adacore.com \
    --to=brobecker@adacore.com \
    --cc=carlos@redhat.com \
    --cc=gti-tac@lists.linuxfoundation.org \
    --cc=joseph@codesourcery.com \
    /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.