From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Tom Coldrick <thomas.coldrick@codethink.co.uk>
Subject: Re: Sourceware Bugzilla Account Creation
Date: Wed, 23 Feb 2022 11:24:07 +0100 [thread overview]
Message-ID: <YhYLR1IsLObUuxGo@wildebeest.org> (raw)
In-Reply-To: <20220223093016.ropd2jl2txrglkb2@menegroth>
Hi Tom,
On Wed, Feb 23, 2022 at 09:30:16AM +0000, Tom Coldrick via Overseers wrote:
> Would it be possible to have an account created for me please? I would like to
> report a bug for glibc.
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
next prev parent reply other threads:[~2022-02-23 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 9:30 Tom Coldrick
2022-02-23 10:24 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-06 11:47 Sourceware Bugzilla account creation Shubham Jangam
2022-04-06 12:14 ` Mark Wielaard
2022-03-16 14:15 Sourceware Bugzilla Account creation Ciaran Woodward
2022-03-16 16:03 ` Mark Wielaard
2022-02-13 0:21 Sourceware bugzilla account creation Gabriel Ravier
2022-02-13 10:03 ` Mark Wielaard
2021-02-20 21:08 SourceWare Bugzilla " Aaron Hill
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=YhYLR1IsLObUuxGo@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=thomas.coldrick@codethink.co.uk \
/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).