From: Khem Raj <raj.khem@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: Logins to glibc wiki does not work
Date: Fri, 24 Jul 2015 20:37:00 -0000 [thread overview]
Message-ID: <AA0D4E8F-D844-487C-AC5E-ED4B30B8A110@gmail.com> (raw)
In-Reply-To: <20150724203101.GA16820@elastic.org>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
> On Jul 24, 2015, at 1:31 PM, Frank Ch. Eigler <fche@elastic.org> wrote:
>
> Hi -
>
>> I have an account for glibc wiki. [...]
>> my user name for wiki is KhemRaj
>
> We run a periodic automatic user deleter script for those who are not
> listed in the EditorGroup list, for anti-spam reasons. I don't see
> you in there (only a "Khem"). Maybe that's the problem.
>
OK may be thats the problem then, can you delete “khem” account and migrate it to “KhemRaj” account
>
> - FChE
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 204 bytes --]
prev parent reply other threads:[~2015-07-24 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 20:19 Khem Raj
2015-07-24 20:31 ` Frank Ch. Eigler
2015-07-24 20:37 ` Khem Raj [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=AA0D4E8F-D844-487C-AC5E-ED4B30B8A110@gmail.com \
--to=raj.khem@gmail.com \
--cc=carlos@redhat.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).