From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Dr. Werner Fink" <werner@suse.de>
Subject: Re: How to report a bug against glibc?
Date: Thu, 7 Jul 2022 13:28:04 +0200 [thread overview]
Message-ID: <YsbDRDA/b8iw5/Vk@wildebeest.org> (raw)
In-Reply-To: <YsbBKdotJuQF8QFL@boole.suse.de>
Hi Werner,
On Thu, Jul 07, 2022 at 01:19:05PM +0200, Dr. Werner Fink via Overseers wrote:
> now as this is a real crash in memset-vec-unaligned-erms.S of glibc I'd like
> to be able to report this, that is I need an account for this.
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-07-07 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 11:19 Dr. Werner Fink
2022-07-07 11:28 ` 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=YsbDRDA/b8iw5/Vk@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=werner@suse.de \
/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).