All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: Bugzilla
Date: Thu, 19 May 2005 06:25:58 +0000	[thread overview]
Message-ID: <20050515201515.GK4435@neu.nirvana> (raw)
In-Reply-To: <3Xg1uAGB.1110214165.5308430.khali@localhost>

On Sun, May 15, 2005 at 10:03:47PM +0200, Jean Delvare wrote:
> Hi Axel,
> 
> > > Sounds better, but what about the drivers? Can there be
> > > subcomponents?
> > 
> > No there are only two levels. If you have a singleton product, you are
> > left with one only.
> > 
> > > The Linux kernel bugzilla has categories and components.
> > 
> > That's the same as products and components. They only replaced
> > "products" in the html pages with "categories" in thir customized
> > bugzilla, but if you query for a "category" you will see
> > http://bugzilla.kernel.org/buglist.cgi?...&product=...
> 
> OK I see. Must be the reason why they do not use a list for version but
> rather a free input. Maybe we should just do the same?

They have dropped the classical version field and patched up bugzilla
to have a new free field "kernel_version". kernel.org picked bugzilla
2.16 and modified it according to their needs. They are now quite
stuck to 2.16 series unless a bugzilla magician helps them migrate.

As long as bugzilla does not offer a nice way to customize it w/o
becoming a maintenance nightmare I'd recommend to not have too many
changes.

The reason for kernel.org to have a free version field is different
than for lm_sensors: kernel.org has a miriad of parallel trees with
complex versioning like 2.6.12-rc1-bk2 or -mm3 etc. lm_sensors has a
normal and simple versioning scheme, e.g. one that doesn't change as
frequently and thus doesn't need too much administrative maintenance.

Discrete versions have also the advantage that you can limit new bug
reports to supported versions.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050515/c852d2a5/attachment.bin

  parent reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 Bugzilla Jean Delvare
2005-05-19  6:25 ` Bugzilla Philip Edelbrock
2005-05-19  6:25 ` Bugzilla Axel Thimm
2005-05-19  6:25 ` Bugzilla Jean Delvare
2005-05-19  6:25 ` Axel Thimm [this message]
2005-05-19  6:25 ` Bugzilla Jean Delvare
2005-05-19  6:25 ` Bugzilla Axel Thimm
2005-05-19  6:25 ` Bugzilla Jean Delvare
  -- strict thread matches above, loose matches on Subject: below --
2009-02-13 13:10 Bugzilla Graeme Fowler
2009-02-13 22:15 ` Bugzilla Simon Horman
2009-02-14  9:49   ` Bugzilla Graeme Fowler
2009-02-15 15:08     ` Bugzilla Graeme Fowler
2009-02-15 22:18       ` Bugzilla Simon Horman
2008-04-29 10:53 Bugzilla Philip Balister
2008-04-29 12:00 ` Bugzilla Leon Woestenberg
2008-04-29 17:30 ` Bugzilla Rolf Leggewie
     [not found] <1042750169.686.6.camel@tux.rsn.bth.se>
     [not found] ` <1042752014.688.12.camel@tux.rsn.bth.se>
2003-01-16 23:50   ` bugzilla Harald Welte

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=20050515201515.GK4435@neu.nirvana \
    --to=axel.thimm@atrpms.net \
    --cc=lm-sensors@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.