public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Zdenek Sojka <zsojka@seznam.cz>
Cc: overseers@sourceware.org
Subject: Re: forwarding gcc PR105744 to the glibc bugzilla
Date: Fri, 27 May 2022 14:41:43 +0200	[thread overview]
Message-ID: <20220527124143.GA25118@tarox.wildebeest.org> (raw)
In-Reply-To: <EZF.28ZR.2zK2DbwSE4F.1YaB1e@scif.cz>

Hi Zdenek,

On Fri, May 27, 2022 at 01:05:12PM +0200, Zdenek Sojka wrote:
> as discussed in the PR?https://gcc.gnu.org/PR105744 I would like to forward 
> it to the glibc bugzilla, but I am failing to create an account with an 
> error:
> 
> User account creation has been restricted.
> 
> Contact your administrator or the maintainer (overseers@sourceware.org) for 
> information about creating an account.

Sorry about that, too many spammes signed up, so we'll authorized
accounts by hand now.

A bugzilla account has been created for you. You should have gotten an
email about it. You can activate your account through the Forgot/Reset
Password link.

Cheers,

Mark

      reply	other threads:[~2022-05-27 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 11:05 Zdenek Sojka
2022-05-27 12:41 ` 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=20220527124143.GA25118@tarox.wildebeest.org \
    --to=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=zsojka@seznam.cz \
    /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).