From: Jerry DeLisle <jvdelisle@charter.net>
To: overseers@sourceware.org
Subject: gcc bugziila write access issue
Date: Fri, 29 Jan 2021 18:16:35 -0800 [thread overview]
Message-ID: <d738c715-c207-f349-93bc-0ff38cd51743@charter.net> (raw)
Hello,
I have write access to the gcc/gfortran source repositories. I have been
contributing to gfortran for well over 10 years.
I noticed recently that although I can comment to the bugzilla bug
reports, I can not update status or 'take' a bug as assigned to me.
I can now only login with userid jvdelisle@charter.net. I had an
account with userid jvdelisle@gcc.gnu.org but do not have that password
for some reason. I can see that jvdelisle@gcc.gnu.org forwards to my
regular email jvdelisle@charter.net.
I tried to reset the password for jvdelisle@gcc.gnu.org but never
recieved an email response to do so.
Can you assist by sending instructions or otherwise to activate the
jvdelisle@gcc.gnu.org with the proper change rights to update the bug
reports as before?
Best regards,
Jerry DeLisle
jvdelisle@charter.net
reply other threads:[~2021-01-30 2:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d738c715-c207-f349-93bc-0ff38cd51743@charter.net \
--to=jvdelisle@charter.net \
--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).