From: "Videau, Brice" <bvideau@anl.gov>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: New Account to Report glibc Bug
Date: Mon, 22 Aug 2022 20:58:40 +0000 [thread overview]
Message-ID: <df72f528-f381-00bf-2b4f-c0931b599721@anl.gov> (raw)
Hello,
I would like to report a bug in glibc and would need a bugzilla account
to do so.
Thanks,
Brice
next reply other threads:[~2022-08-22 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 20:58 Videau, Brice [this message]
2022-08-23 7:18 ` 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=df72f528-f381-00bf-2b4f-c0931b599721@anl.gov \
--to=bvideau@anl.gov \
--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).