linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org
Date: Mon, 11 Jan 2021 10:14:07 -0800	[thread overview]
Message-ID: <6ca51584-1739-e532-d40e-e4447065ea1e@infradead.org> (raw)
In-Reply-To: <20210110121033.130504-1-linux@leemhuis.info>

On 1/10/21 4:10 AM, Thorsten Leemhuis wrote:
> * About 66 of those ~200 components will assign bugs to email addresses
>   that look valid, but 125 of them end with @kernel-bugs.osdl.org or
>   @kernel-bugs.kernel.org. Those domains do not exist anymore, mails
>   sent there bounce ('Unrouteable address'). It's possible that the
>   server might be rewriting those domain names and nevertheless
>   delivers new reports and comments by mails to some human; but it
>   seems more like they never get mailed to anyone and thus just linger
>   in the database; no wonder quite a few of bugs filed against such
>   components never get a single reply (see below).

Those @kernel-bugs email addresses should not be a problem:

  https://korg.docs.kernel.org/bugzilla.html#real-assignees-vs-virtual-assignees



AFAIK, USB bugs go to linux-usb@vger.kernel.org,
SCSI bugs go to linux-scsi@vger.kernel.org.

netdev didn't want bugs sent there automatically IIRC, so a
human takes care of doing that if warranted.

Andrew Morton takes MM bugs and Cc:s them to linux-mm mailing list
and then asks for discussion to continue on the mailing list.


We could/should probably see if we can add more project-specific
mailing lists to the automatic reporting -- but probably not LKML.

Otherwise some bug reports might never be heard about.

-- 
~Randy


  reply	other threads:[~2021-01-11 18:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 12:10 [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org Thorsten Leemhuis
2021-01-11 18:14 ` Randy Dunlap [this message]
2021-01-11 18:55   ` Thorsten Leemhuis
2021-01-11 23:42     ` Randy Dunlap
2021-01-12 17:34       ` Thorsten Leemhuis
2021-01-11 19:48 ` Konstantin Ryabitsev
2021-01-12 19:09   ` Thorsten Leemhuis
2021-01-13 11:17     ` Jani Nikula
2021-01-14 19:18       ` Konstantin Ryabitsev
2021-11-05 14:36 ` Artem S. Tashkinov
2021-11-05 14:42   ` Matthew Wilcox
2021-11-05 14:59     ` Artem S. Tashkinov
2021-11-08 11:43   ` Jani Nikula
2021-11-08 12:03     ` Artem S. Tashkinov
2021-11-08 13:00       ` Jani Nikula
2021-11-08 13:17         ` Artem S. Tashkinov

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=6ca51584-1739-e532-d40e-e4447065ea1e@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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).