From: Joseph Myers <joseph@codesourcery.com>
To: "Frank Ch. Eigler via Overseers" <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Joel Brobecker <brobecker@adacore.com>,
Mark Wielaard <mark@klomp.org>,
Simon Marchi <simon.marchi@polymtl.ca>,
Pedro Alves <pedro@palves.net>
Subject: Re: getting spammed on bugzilla
Date: Thu, 25 Nov 2021 17:59:08 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2111251758110.1751940@digraph.polyomino.org.uk> (raw)
In-Reply-To: <YZ/N0TudlvN/Vtzn@elastic.org>
On Thu, 25 Nov 2021, Frank Ch. Eigler via Overseers wrote:
> Hi -
>
> On Thu, Nov 25, 2021 at 05:49:39PM +0000, Joseph Myers wrote:
> > [...]
> > > Ummmmmmmmmmmm about that. How is this part supposed to work on gcc's
> > > bugzilla? I just made myself a test user there, with no one else's
> > > approval [...]
> >
> > See extensions/GCC/lib/Constants.pm, BLACKLISTED_DOMAINS. The idea is
> > that users of a range of typically free webmail domains have to go through
> > the manual account creation process, while users with other domains
> > (personal, corporate, academic, etc.) can typically create their own
> > accounts without needing manual approval. [...]
>
> Ah. My vanity domain must not be blacklisted, whew. After that
> email, earlier today, I "fixed" gcc bugzilla to direct all account
> requests through to the gcc bugzilla-account-requester list. Would
> you like this set back, or shall we try the new non-discriminating
> "everyone gets to ask" format for a while?
I think it should be set back so account requests are only needed for
blacklisted domains such as gmail.com.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-11-25 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:29 Joel Brobecker
2021-11-11 3:47 ` Andrew Pinski
2021-11-12 4:40 ` Joel Brobecker
2021-11-12 8:55 ` Mark Wielaard
2021-11-12 13:26 ` Carlos O'Donell
2021-11-22 4:03 ` Joel Brobecker
2021-11-24 10:09 ` Mark Wielaard
2021-11-24 14:55 ` Frank Ch. Eigler
2021-11-24 23:40 ` Mark Wielaard
2021-11-25 0:19 ` Frank Ch. Eigler
2021-11-25 17:49 ` Joseph Myers
2021-11-25 17:54 ` Frank Ch. Eigler
2021-11-25 17:59 ` Joseph Myers [this message]
2021-11-28 17:01 ` Mark Wielaard
2021-11-28 17:35 ` Frank Ch. Eigler
2021-11-28 18:07 ` Mark Wielaard
2021-11-29 17:12 ` Joseph Myers
2021-12-17 2:50 ` Joel Brobecker
2021-12-17 17:19 ` Frank Ch. Eigler
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=alpine.DEB.2.22.394.2111251758110.1751940@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
/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).