public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30936] New: New private mailing list: glibc-cna@sourceware.org
Date: Tue, 03 Oct 2023 10:39:46 +0000	[thread overview]
Message-ID: <bug-30936-14326@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30936

            Bug ID: 30936
           Summary: New private mailing list: glibc-cna at sourceware dot org
           Product: sourceware
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Infrastructure
          Assignee: overseers at sourceware dot org
          Reporter: siddhesh at sourceware dot org
                CC: adhemerval.zanella at linaro dot org, carlos at redhat dot com
  Target Milestone: ---

The glibc project will be registering a CNA under Red Hat and we need a private
contact point to receive security reports. Could you please create a
glibc-cna@sourceware.org private mailing list that will forward to named
members of the community?  The list should not allow arbitrary membership, but
should allow unregistered folks to send mail to the list.  The bootstrap
members are me, adhemerval and carlos.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2023-10-03 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 10:39 siddhesh at sourceware dot org [this message]
2023-10-03 23:07 ` [Bug Infrastructure/30936] " mark at klomp dot org
2023-10-11 11:02 ` siddhesh at sourceware dot org
2023-10-11 11:37 ` 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-30936-14326@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).