From: Nick Alcock <nick.alcock@oracle.com>
To: overseers@sourceware.org
Subject: Re: Spurious bz "inappropriate content" rejection and now my bz account is locked
Date: Fri, 19 Feb 2021 16:59:40 +0000 [thread overview]
Message-ID: <878s7kxabn.fsf@esperi.org.uk> (raw)
In-Reply-To: <87sg6eigzm.fsf@esperi.org.uk> (Nick Alcock's message of "Tue, 02 Feb 2021 16:14:53 +0000")
On 2 Feb 2021, Nick Alcock uttered the following:
> So I just tried to submit a bug report with this content against
> gdbserver:
[...]
>> Subject: gdbserver fails to build with --with-included-gettext
>
>> (Caveat: not currently reproducible on platforms with Bison 3.0+
[...]
> A longer (untrimmed) version was rejected due to "inappropriate
> content". Trying to add this version instead asked me to log into bz
> (even though I was already logged in), then auto-locked my account "due
> to spam".
>
> Please can you unlock it, and if possible figure out what is causing
> this false positive rejection and fix it?
>
> Thanks!
Ping? (My account still seems to be "auto-locked due to spam.")
next prev parent reply other threads:[~2021-02-19 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 16:14 Nick Alcock
2021-02-19 16:59 ` Nick Alcock [this message]
2021-02-19 17:04 ` 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=878s7kxabn.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--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).