From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Dealing with bugzilla
Date: Thu, 19 Sep 2024 09:10:46 -0700 [thread overview]
Message-ID: <20240919091046.64cb49b6@hermes.local> (raw)
Up until now, I have been the volunteer screener of networking related bugzilla bugs.
I would like to get out of doing that.
The alternatives are:
1. Change the bugzilla forwarding to netdev@vger.kernel.org (ie no screening)
2. Get a new volunteer to screen
3. Make a new mailing list target on vger (ie netdev-bugs@vger.kernel.org)
4. Find someone to make a bot to use get_maintainer somehow to forward
5. Blackhole the bugzilla reports.
6. Bounce all the bugzilla reports somehow.
Any suggestions welcome.
next reply other threads:[~2024-09-19 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 16:10 Stephen Hemminger [this message]
2024-09-19 16:17 ` Dealing with bugzilla Florian Westphal
2024-09-19 16:43 ` Stephen Hemminger
2024-09-19 23:06 ` Jacob Keller
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=20240919091046.64cb49b6@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.