From: Carlos O'Donell <carlos@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: aral <aral@gmx.de>
Subject: Re: How to deal with "User account creation has been restricted."
Date: Wed, 9 Feb 2022 11:15:58 -0500 [thread overview]
Message-ID: <914c79a4-24e7-f195-7611-44015d2916eb@redhat.com> (raw)
In-Reply-To: <20883fc7-315b-fdd8-d512-397eec34af99@gmx.de>
On 2/9/22 10:49, aral via Overseers wrote:
> Dear admins,
>
> I could not create an account for the Sourceware Bugzilla right now
> using this e-mail address can you tell me how to proceed?
>
> Also: If the "bug" is a valid implementation of the Open Group Base
> Specifications, and I believe that a slight modification of the
> implementation is possible, while staying compliant with the standard -
> where would be the proper platform to suggest this?
>
> This concerns the dlfcn library / functions dlclose / dlopen.
>
> Thank you for a response!
I've setup your account and sent you the details.
--
Cheers,
Carlos.
prev parent reply other threads:[~2022-02-09 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 15:49 aral
2022-02-09 16:15 ` Carlos O'Donell [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=914c79a4-24e7-f195-7611-44015d2916eb@redhat.com \
--to=carlos@redhat.com \
--cc=aral@gmx.de \
--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).