From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "François Dumont via Overseers" <overseers@sourceware.org>,
overseers@gcc.gnu.org, "François Dumont" <frs.dumont@gmail.com>
Subject: Re: gcc git write access
Date: Sat, 25 Mar 2023 21:44:48 +0000 [thread overview]
Message-ID: <CAH6eHdRCxwH-8GCKzmrV3DEmm1pKsUJ3YdbphYjy3M3BnW3BPQ@mail.gmail.com> (raw)
In-Reply-To: <20230325184258.GJ4011@gnu.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
I don't remember which address François used previously, but I can confirm
this is the address he's been using for all recent gcc commits.
I can't confirm that his Gmail account hasn't been hacked of course ;-)
On Sat, 25 Mar 2023, 18:42 Mark Wielaard, <mark@klomp.org> wrote:
> Hi François,
>
> On Sat, Mar 25, 2023 at 02:46:32PM +0100, François Dumont via Overseers
> wrote:
> > Sorry to bother you but I've lost my system and with it my ssh
> > public key for my fdumont gcc git repo write access. Is it possible
> > to reset it with my new attached one ?
>
> Note that we handle account requests through
> admin-requests@sourceware.org these days.
>
> This isn't the address on record for you in gcc MAINTAINERS and it
> isn't the address you originally used to get your account. Would you
> be able to sent a request from that address to
> admin-requests@sourceware.org to verify it is you?
>
> Thanks,
>
> Mark
>
>
>
next prev parent reply other threads:[~2023-03-25 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <845d35fc-5e99-1b62-88d7-26506585cb6e@gmail.com>
2023-03-25 18:42 ` Mark Wielaard
2023-03-25 21:44 ` Jonathan Wakely [this message]
[not found] <1688581769729.6.48448@webmail-backend-production-7b8b7bc877-5lcfq>
2023-07-05 20:50 ` Mark Wielaard
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=CAH6eHdRCxwH-8GCKzmrV3DEmm1pKsUJ3YdbphYjy3M3BnW3BPQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=frs.dumont@gmail.com \
--cc=mark@klomp.org \
--cc=overseers@gcc.gnu.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).