From: "Arkadiusz Hiler" <arek@hiler.eu>
To: "overseers" <overseers@sourceware.org>
Subject: account for reporting glibc bugs
Date: Sat, 06 Aug 2022 02:55:29 +0300 (EEST) [thread overview]
Message-ID: <E1oK7A9-0004p2-I2@rmmprod07.runbox> (raw)
Hi,
I need an account to create a bug for glibc.
Cheers,
Arek
next reply other threads:[~2022-08-05 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 23:55 Arkadiusz Hiler [this message]
2022-08-06 10:33 ` 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=E1oK7A9-0004p2-I2@rmmprod07.runbox \
--to=arek@hiler.eu \
--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).