From: "Theodore Ts'o" <tytso@mit.edu>
To: Nick Krause <xerofoify@gmail.com>
Cc: stable@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Cleanup of Kernel Bugzilla
Date: Sat, 28 Jun 2014 12:36:18 -0400 [thread overview]
Message-ID: <20140628163618.GC22215@thunk.org> (raw)
In-Reply-To: <CAPDOMVjnROuS4D4E2B7=PxOZUB4YXHuFUKy5C9Y8Lm7gxN=N_Q@mail.gmail.com>
On Fri, Jun 27, 2014 at 10:45:47PM -0400, Nick Krause wrote:
> Do any of you use the kernel Bugzilla? If you do I was wondering if we
> can clean it up.
> Otherwise I was wondering were I can get an accurate list of open
> bugs in the newest
> kernels.
Some subsystem maintainers use the kernel bugzilla. Others do not.
How they use it is also highly variable. For example, bugs that are
filed with the ext4 component cause mail to be sent to the linux-ext4
mailing list, and replies automatically end up in the bugzilla log.
We use the ext4 bugzilla as a record of the bug, and we'll have a
pointer to the kernel bugzilla URL with the fix. But we don't always
close out the bug. Sometimes a few kernel developers will do some
cleanup, but it's not something that done regularly.
Also note that many bugs are never filed via the bugzilla, and are
reported via the mailing list. So if you want a full and complete
list of open bugs --- sorry, there is no such thing.
- Ted
next prev parent reply other threads:[~2014-06-28 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 18:11 Cleanup of Kernel Bugzilla Nick Krause
2014-06-28 2:45 ` Nick Krause
2014-06-28 16:06 ` Nick Krause
2014-06-28 16:55 ` Theodore Ts'o
2014-06-28 16:36 ` Theodore Ts'o [this message]
2014-06-28 19:18 ` One Thousand Gnomes
2014-06-29 3:04 ` Nick Krause
2014-06-29 6:33 ` Gideon D'souza
2014-06-29 7:21 ` Levente Kurusa
2014-06-29 21:32 ` Theodore Ts'o
2014-06-30 2:09 ` Nick Krause
2014-06-30 12:42 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2014-06-27 2:44 Nick Krause
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=20140628163618.GC22215@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xerofoify@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