From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
binutils@sourceware.org, gdb@sourceware.org
Subject: Sourceware Open Office, Friday 16:00 UTC
Date: Wed, 12 Jun 2024 23:09:32 +0200 [thread overview]
Message-ID: <20240612210932.GJ21923@gnu.wildebeest.org> (raw)
Friday June 14, 16:00 UTC, irc.libera.chat #overseers
To get the right time in your local timezone:
$ date -d "Fri May 10 16:00:00 UTC 2024"
- Discussion topic:
https://sourceware.org/sourceware-security-vision.html
The Sourceware infrastructure security vision explains what
Sourceware is, the mission, how the organization works, the secure
Sourceware project goals and plans. This includes not just
infrastructure services updates, but also the secure software
development framework projects use and secure supply chain issues.
But feel free to drop in with any question or suggestion you have
related to Sourceware infrastructure.
next reply other threads:[~2024-06-12 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 21:09 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-10 15:05 Mark Wielaard
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=20240612210932.GJ21923@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=overseers@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).