From: Pieter-Jan Briers <pieterjan.briers@gmail.com>
To: overseers@sourceware.org
Subject: Would like to create a bugzilla account to report glibc bug.
Date: Thu, 3 Mar 2022 09:16:40 +0100 [thread overview]
Message-ID: <1634e554-b052-87bb-2f51-eb54f96dc4c8@gmail.com> (raw)
Hi,
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.
Could I be allowed to make an account?
Thanks in advance
[1]: https://bugs.archlinux.org/task/73967
next reply other threads:[~2022-03-03 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 8:16 Pieter-Jan Briers [this message]
2022-03-03 12:22 ` 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=1634e554-b052-87bb-2f51-eb54f96dc4c8@gmail.com \
--to=pieterjan.briers@gmail.com \
--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).