From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Pieter-Jan Briers <pieterjan.briers@gmail.com>
Subject: Re: Would like to create a bugzilla account to report glibc bug.
Date: Thu, 3 Mar 2022 13:22:13 +0100 [thread overview]
Message-ID: <YiCy9YMnlx5TXFig@wildebeest.org> (raw)
In-Reply-To: <1634e554-b052-87bb-2f51-eb54f96dc4c8@gmail.com>
Hi Pieter-Jan,
On Thu, Mar 03, 2022 at 09:16:40AM +0100, Pieter-Jan Briers via Overseers wrote:
> I found a somewhat severe bug in glibc[1] that I would like to report, but
> account creation on bugzilla is currently restricted it seems like.
A bugzilla account has been created for you. You should have gotten an
email about it. You can activate your account through the Forgot/Reset
Password link.
Cheers,
Mark
prev parent reply other threads:[~2022-03-03 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 8:16 Pieter-Jan Briers
2022-03-03 12:22 ` Mark Wielaard [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=YiCy9YMnlx5TXFig@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pieterjan.briers@gmail.com \
/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).