From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Sunil Pandey <skpgkp2@gmail.com>
Subject: Re: account locked.
Date: Sun, 7 Jun 2020 23:32:09 +0200 [thread overview]
Message-ID: <20200607213209.GD2832@wildebeest.org> (raw)
In-Reply-To: <CAMAf5_f1j+DM6RjhE7oGnYYrrOdotzXcwLRuYgOMxqh8jVOkRA@mail.gmail.com>
Hi,
On Sun, Jun 07, 2020 at 02:10:10PM -0700, Sunil Pandey via Overseers wrote:
> My account(skpgkp2@gmail.com) got locked while updating the bug report. I
> believe my account should be restored. I don't see anything inappropriate
> about updating a bug report with the following status update. It got locked
> while updating this bug.
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=25933
>
> Can you please take a look and let me know which word I shouldn't use in
> future to avoid this problem.
I have enabled your bugzilla account again.
Unfortunately I cannot tell what exactly triggered the spam ban.
None of your (other) comments look like spam to me.
Cheers,
Mark
next prev parent reply other threads:[~2020-06-07 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 21:10 Sunil Pandey
2020-06-07 21:32 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-05 18:53 Reinoud Koornstra
2019-11-05 18:59 ` Frank Ch. Eigler
2019-11-05 20:56 ` Reinoud Koornstra
2019-11-05 20:57 ` 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=20200607213209.GD2832@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=skpgkp2@gmail.com \
/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).