From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Roger Sayle <roger@nextmovesoftware.com>
Subject: Re: Redirecting sayle@gcc.gnu.org
Date: Wed, 12 Aug 2020 13:48:17 +0200 [thread overview]
Message-ID: <20200812114817.GC18573@wildebeest.org> (raw)
In-Reply-To: <004501d67086$ee5cb530$cb161f90$@nextmovesoftware.com>
Hi Roger,
On Wed, Aug 12, 2020 at 09:59:46AM +0100, Roger Sayle via Overseers wrote:
> Please can I ask you to change the redirect for e-mail to sayle@gcc.gnu.org to deliver to my
> current e-mail address (roger@nextmovesoftware.com) from a (much) older and now invalid
> e-mail address (roger@eyesopen.com). E-mail sent to sayle@gnu.org is already being
> directed to correct place, but I hadn't realized until this morning that adding the "gcc."
> in the middle causes messages to disappear in a black hole.
You should be able to do that yourself:
$ ssh sourceware.org email roger@nextmovesoftware.com
See also https://sourceware.org/sourceware/accountinfo.html
> p.s. Is there something I need to do to get/restore permissions in GCC Bugzilla for my
> "roger@nextmovesoftware.com" account. I don’t appear to be able to change the
> status or close bugs (like I used to), but this may be user error on my end.
If you use sayle@gcc.gnu.org as account then you get these permissions automatically.
But I have added roger@nextmovesoftware.com to the editbugs group.
Cheers,
Mark
prev parent reply other threads:[~2020-08-12 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 8:59 Roger Sayle
2020-08-12 11:48 ` Mark Wielaard [this message]
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=20200812114817.GC18573@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.org \
--cc=roger@nextmovesoftware.com \
/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).