From: ellis@spinics.net
To: mtk.manpages@gmail.com
Cc: mricon@kernel.org (Konstantin Ryabitsev),
linux-man@vger.kernel.org (linux-man),
linux-kernel@vger.kernel.org (lkml)
Subject: Re: Bugzilla spam
Date: Wed, 13 Jul 2016 14:35:14 -0700 (PDT) [thread overview]
Message-ID: <201607132135.u6DLZEvS030590@spinics.net> (raw)
In-Reply-To: <CAKgNAkjS5EW4d0mw6N_CvQAY11uY8hPXiLk_WXMcU1J=ojLmzA@mail.gmail.com>
> Okay, thanks. In the meantime, is it possible for you to lock the
> man-pages component so that no further bug reports can be made via
> that component?
It's not just the man-pages component. I'm seeing the same spam starting
up on backports.
prev parent reply other threads:[~2016-07-13 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 18:28 Bugzilla spam Michael Kerrisk (man-pages)
2016-07-13 18:37 ` Konstantin Ryabitsev
2016-07-13 18:48 ` Michael Kerrisk (man-pages)
2016-07-13 21:35 ` ellis [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=201607132135.u6DLZEvS030590@spinics.net \
--to=ellis@spinics.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mricon@kernel.org \
--cc=mtk.manpages@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 NNTP newsgroup(s).