From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: overseers@sourceware.org
Subject: Sourceware bugzilla account creation request
Date: Mon, 22 Aug 2022 00:17:26 +0200 [thread overview]
Message-ID: <20220821221726.ggamr5jiapuhbrc3@tarta.nabijaczleweli.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 152 bytes --]
Hi!
Aurelien told me to forward this glibc bug from Debian:
https://bugs.debian.org/1017852
But I need a bugzilla account :)
Best,
наб
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-08-21 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 22:17 наб [this message]
2022-08-21 22:34 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2022-04-14 17:25 Sourceware Bugzilla " Zhenyang Xu
2022-04-14 18:15 ` Frank Ch. Eigler
2022-02-04 23:38 Alexander Kernozhitsky
2022-02-05 0:05 ` 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=20220821221726.ggamr5jiapuhbrc3@tarta.nabijaczleweli.xyz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--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).