From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29629] Does the server need to meet NIST SP 800-53?
Date: Wed, 28 Sep 2022 13:14:09 +0000 [thread overview]
Message-ID: <bug-29629-14326-WZkUqxH6qc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29629-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29629
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Answering the "does this apply?" question is a regulatory or legal matter if
anything. Do you know? If not, what is the infrastructure action you propose?
Answering the "would it expand FOSS usage" question is not something we can
know, nor an infrastructure matter.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-09-28 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 12:48 [Bug Infrastructure/29629] New: " carlos at redhat dot com
2022-09-28 13:14 ` fche at redhat dot com [this message]
2022-10-06 17:59 ` [Bug Infrastructure/29629] " mark at klomp dot org
2022-10-14 17:28 ` fche at redhat dot com
2022-10-21 13:25 ` fche at redhat dot com
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=bug-29629-14326-WZkUqxH6qc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).