public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Paul-Antoine Arras <pa@codesourcery.com>
To: <overseers@gcc.gnu.org>
Subject: Fwd: Log into Bugzilla as parras@gcc.gnu.org
Date: Tue, 27 Sep 2022 16:32:16 +0200	[thread overview]
Message-ID: <7a005415-c14e-c538-1d4b-93a1ddda74f5@codesourcery.com> (raw)
In-Reply-To: <CAH6eHdSqb6ShVWuuMWYu0-wEW_RZp2nsuWTRQNZMNEDN5Tx_CQ@mail.gmail.com>

Hello,

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?

PA

-------- Forwarded Message --------
Subject: Re: Log into Bugzilla as parras@gcc.gnu.org
Date: Tue, 27 Sep 2022 15:23:57 +0100
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Paul-Antoine Arras <pa@codesourcery.com>
CC: gcc-bugzilla-account-request@gcc.gnu.org

I would expect that to work. The email for parras@gcc.gnu.org should
go to this account, pa@codesourcery.com (because that's what
~parras/.forward says on gcc.gnu.org).

Have you checked your spam folder? Give it another try, and if the
email still doesn't turn up you'll have to contact the overseers on
IRC or by email. We don't deal with creating the @gcc.gnu.org accounts
here.

       reply	other threads:[~2022-09-27 14:32 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 [this message]
2022-09-27 14:58   ` Frank Ch. Eigler
2022-09-27 16:16     ` Paul-Antoine Arras
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=7a005415-c14e-c538-1d4b-93a1ddda74f5@codesourcery.com \
    --to=pa@codesourcery.com \
    --cc=overseers@gcc.gnu.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).