From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Provide a SECURITY.md for glibc.
Date: Wed, 5 Apr 2023 15:24:43 -0400 [thread overview]
Message-ID: <3bba36db-1422-61b4-2411-e11628087aef@gotplt.org> (raw)
In-Reply-To: <1707ded6-1f65-447e-6cef-599241524ef6@gotplt.org>
On 2023-03-27 09:18, Siddhesh Poyarekar wrote:
> On 2023-02-23 14:15, Carlos O'Donell via Libc-alpha wrote:
>> Github itself can be configured with a security policy around this topic:
>> https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository
>
> Maybe this should be noted in the git commit log for posterity.
Also, I wonder if it makes sense to move all of that content off the
wiki and into the SECURITY.md.
Thanks,
Sid
prev parent reply other threads:[~2023-04-05 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 17:19 Carlos O'Donell
2023-02-23 11:44 ` Florian Weimer
2023-02-23 19:15 ` Carlos O'Donell
2023-03-27 13:18 ` Siddhesh Poyarekar
2023-04-05 19:24 ` Siddhesh Poyarekar [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=3bba36db-1422-61b4-2411-e11628087aef@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=fweimer@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).