From: Nicholas Krause <xerofoify@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org
Subject: Re: Wiki Account Issues with GCC Wiki
Date: Mon, 16 Dec 2019 18:27:00 -0000 [thread overview]
Message-ID: <41d8cd98-4c0b-b708-26dc-b0abae4a2cc7@gmail.com> (raw)
In-Reply-To: <20191216180851.GB65548@elastic.org>
On 12/16/19 1:08 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> I'm pinging this as its been about or little over a week and I'm not
>> heard back about resolving my account issues on the GCC wiki.
> wiki accounts automatically get nuked every Saturday(ish) if they are
> not listed in that wiki's trusted-editors page. So chances are that
> you can recreate this account from scratch, named just the way you'd
> like it, and then ping wiki editors to add you.
>
> - FChE
My account emails but the email is set incorrectly so I'm not getting a
password reset token. The account is NicholasKrause and its this
email that it would be need to be sent to.
Nick
next prev parent reply other threads:[~2019-12-16 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 0:19 Nicholas Krause
2019-12-16 18:07 ` Nicholas Krause
2019-12-16 18:08 ` Frank Ch. Eigler
2019-12-16 18:27 ` Nicholas Krause [this message]
2020-01-06 23:00 ` Nicholas Krause
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=41d8cd98-4c0b-b708-26dc-b0abae4a2cc7@gmail.com \
--to=xerofoify@gmail.com \
--cc=fche@elastic.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).