From: Paul-Antoine Arras <pa@codesourcery.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Subject: Re: Fwd: Log into Bugzilla as parras@gcc.gnu.org
Date: Tue, 27 Sep 2022 18:16:48 +0200 [thread overview]
Message-ID: <960695e6-7c2f-1e3e-e202-0a31809f628f@codesourcery.com> (raw)
In-Reply-To: <YzMPiebBciFptXWx@elastic.org>
Hi Frank,
On 27/09/2022 16:58, Frank Ch. Eigler wrote:
>> I have a gcc.gnu.org account with login "parras". I do not have a
>> password on Bugzilla yet though. So I tried the "Forgotten password" but
>> did not receive any token to set a new password.
>> Am I doing something wrong?
>
> I think you never had a gcc.gnu.org/bugzilla account created at all.
> That's a distinct thing from gcc git committer access. I've now
> created one for you.
Thank you for creating the Bugzilla account. However, I am still not
receiving the token to set a password after entering parras@gnu.gcc.org
in the "Forgot password" field.
Any insight into that?
--
PA
next prev parent reply other threads:[~2022-09-27 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH6eHdSqb6ShVWuuMWYu0-wEW_RZp2nsuWTRQNZMNEDN5Tx_CQ@mail.gmail.com>
2022-09-27 14:32 ` Paul-Antoine Arras
2022-09-27 14:58 ` Frank Ch. Eigler
2022-09-27 16:16 ` Paul-Antoine Arras [this message]
2022-09-27 16:20 ` Frank Ch. Eigler
2022-09-27 16:35 ` Paul-Antoine Arras
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=960695e6-7c2f-1e3e-e202-0a31809f628f@codesourcery.com \
--to=pa@codesourcery.com \
--cc=fche@elastic.org \
--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).