From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Alex Diaz <alex@eadem.com>
Subject: Re: bug confirmed by valgrind team
Date: Sun, 23 Jan 2022 18:02:28 +0100 [thread overview]
Message-ID: <Ye2KJOOLUWxIZmVB@wildebeest.org> (raw)
In-Reply-To: <CACZoT5YM7tO7w0S5_AjrT5ajfOdBHiLgG4hqRVh9W3AgfkG2QQ@mail.gmail.com>
Hi Alex,
On Sun, Jan 23, 2022 at 08:54:32AM -0800, Alex Diaz via Overseers wrote:
> Hello, I'm unable to open an account. I'd like to report a bug confirmed by
> the valgrind team.
An 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
next prev parent reply other threads:[~2022-01-23 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 16:54 Alex Diaz
2022-01-23 17:02 ` Mark Wielaard [this message]
2022-01-23 20:03 ` Alex Diaz
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=Ye2KJOOLUWxIZmVB@wildebeest.org \
--to=mark@klomp.org \
--cc=alex@eadem.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).