public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Bugzilla Account/Email Forwarding
Date: Mon, 1 Aug 2022 15:19:14 -0500	[thread overview]
Message-ID: <CAF9ehCX=RYN=wmScWC_NZ2wQcNO0eFtUY7YsDH2J_jQHVVqDFg@mail.gmail.com> (raw)
In-Reply-To: <YugxgEX73cuNzuL1@wildebeest.org>

On Mon, Aug 1, 2022 at 3:03 PM Mark Wielaard <mark@klomp.org> wrote:

> Hi Joel,
>
> On Mon, Aug 01, 2022 at 02:37:42PM -0500, Joel Sherrill via Overseers
> wrote:
> > I have used joel@gcc.gnu.org for years as my Sourceware Bugzilla account
> > name. I apparently have lost the password for Bugzilla and requested a
> > reset password email. I didn't get any email which makes me wonder where
> > joel@gcc.gnu.org is forwarding.
>

Thanks for the quick response.

>
> It should be forwarding to joel@rtems.org. If you have access to your
> gcc.gnu.org account then you should be able to change that yourself,
> see https://sourceware.org/sourceware/accountinfo.html


I confirmed I can login and I sent a test email from my work account to
joel@gcc.gnu.org. It showed up in my gmail inbox so forwarding must
work.

>
>
> Although that doesn't really explain why you didn't get a reset
> password.  I'll see if I can reset my own password.
>

I tried again and didn't get one. I have looked in spam.

--joel

>
> Cheers,
>
> Mark
>

  reply	other threads:[~2022-08-01 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 19:37 Joel Sherrill
2022-08-01 20:03 ` Mark Wielaard
2022-08-01 20:19   ` Joel Sherrill [this message]
2022-08-01 20:25   ` Mark Wielaard
2022-08-01 20:36     ` Joel Sherrill
2022-08-01 21:14       ` Joel Sherrill

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='CAF9ehCX=RYN=wmScWC_NZ2wQcNO0eFtUY7YsDH2J_jQHVVqDFg@mail.gmail.com' \
    --to=joel@rtems.org \
    --cc=mark@klomp.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).