From: "Carlos O'Donell" <carlos@redhat.com>
To: gcc <gcc@gcc.gnu.org>, glibc <libc-alpha@sourceware.org>,
binutils <binutils@sourceware.org>, gdb <gdb@sourceware.org>,
David Edelsohn <dje.gcc@gmail.com>,
David Malcolm <dmalcolm@redhat.com>,
Guinevere Larsen <blarsen@redhat.com>,
Jason Merrill <jason@redhat.com>
Subject: Office Hours for the GNU Toolchain on 2024-03-28 at 11am EST5EDT.
Date: Tue, 19 Mar 2024 12:11:00 -0500 [thread overview]
Message-ID: <CAEMqeSq0kN+KWGpKBt6Q+mJFBvCSgBzeAKOdngD58mYzc5KGMA@mail.gmail.com> (raw)
Office Hours for the GNU Toolchain on 2024-03-28 at 11am EST5EDT.
Agenda:
* https://gcc.gnu.org/wiki/OfficeHours#Next
Meeting Link:
* https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6
--
Cheers,
Carlos.
reply other threads:[~2024-03-19 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAEMqeSq0kN+KWGpKBt6Q+mJFBvCSgBzeAKOdngD58mYzc5KGMA@mail.gmail.com \
--to=carlos@redhat.com \
--cc=binutils@sourceware.org \
--cc=blarsen@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jason@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).