public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@dsv.su.se>
To: linux-kernel@vger.kernel.org
Cc: zwane@holomorphy.com, akpm@osdl.org
Subject: The bugzilla story
Date: Mon, 06 Dec 2004 15:22:40 +0100	[thread overview]
Message-ID: <1102342960.727.59.camel@boxen> (raw)

Hi

As some of you may have noticed I've been doing a run on bugzilla for
the last few days to close old bugs and upgrade those who still are real
bugs.

I have a few things that I would like to enforce on bugzilla to makes it
more maintanable which it clearly hasn't been for a while - there are
lots and lots of bugs open older than 2.6.0-final.

I think the alternative trees section should be dropped. This is
especially a matter for -mm which has most reports of the alternative
trees in bugzilla. -mm changes way too rapidly to keep track of at
bugzilla ending up with open bugs that are fixed long ago.

I also think this goes for any alternative tree, that problems should be
reported directly to the maintainer/LKML of the tree. Only if a problem
can be reproduced with the mainline kernel should the bug be reported at
bugzilla. 

New bugzilla reports against other trees than mainline should be
rejected and ask the submitter to report directly to the
maintainer/LKML.

Andrew, what do you think about bug reports against -mm on bugzilla?

Does anyone see a problem with this? 

Thanks
Alexander


             reply	other threads:[~2004-12-06 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 14:22 Alexander Nyberg [this message]
2004-12-06 15:03 ` The bugzilla story Zwane Mwaikambo
2004-12-06 15:28 ` Martin J. Bligh
2004-12-06 16:26   ` Alexander Nyberg
2004-12-06 16:14     ` Alan Cox
2004-12-06 23:15       ` Rafael J. Wysocki
2004-12-08  1:14 ` Jeff Garzik

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=1102342960.727.59.camel@boxen \
    --to=alexn@dsv.su.se \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@holomorphy.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