From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: William Tang <galaxyking0419@gmail.com>
Subject: Re: Need an account for bug report
Date: Wed, 13 Apr 2022 11:45:13 +0200 [thread overview]
Message-ID: <YlabqVZfusrtthge@wildebeest.org> (raw)
In-Reply-To: <CABsZaPj_pF4h4HCSCeCyyMQ-dKdmbuwER41qf9eSasYJDG8O_A@mail.gmail.com>
Hi William,
On Wed, Apr 13, 2022 at 10:54:05AM +0800, William Tang via Overseers wrote:
> Can I have an account for bug reporting?
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-04-13 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 2:54 William Tang
2022-04-13 9:45 ` 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=YlabqVZfusrtthge@wildebeest.org \
--to=mark@klomp.org \
--cc=galaxyking0419@gmail.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).