From: "Andreas Kuckartz" <A.Kuckartz@ping.de>
To: Sam Vilain <sam@vilain.net>
Cc: alsa-user@lists.sourceforge.net, <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-user] Re: Bugtracking system
Date: 23 Jan 2004 10:59:12 +0100 [thread overview]
Message-ID: <012b01c3e198$4ccb0d00$a501a8c0@computer2> (raw)
In-Reply-To: 200401231545.41284.sam@vilain.net
Sam Vilain wrote:
> What about sub-sub-categories for attaching bugs to individual
> drivers?
That is not supported by Bugzilla. One possibility is to remove one level
and add something like "ALSA drivers" as a second separate top-level
Category with the main drivers as individual Components. I think that can
and should be done later when the use of bugzilla.kernel.org is established.
The Bugzilla administrator probably would hesitate to do that now before it
is known that the system is really used for ALSA bugtracking. (There is not
yet a single entry for the whole current "Alternate Trees" Category ...)
Cheers,
Andreas
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-23 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a662904be22869df6c18097e559e8a7b@localhost.localdomain>
[not found] ` <1074646711.2067.15.camel@Wizard.knechthome.com>
2004-01-21 10:48 ` Bugtracking system Andreas Kuckartz
2004-01-21 10:56 ` Dan Hollis
2004-01-21 12:26 ` Re: [Alsa-devel] " Andreas Kuckartz
2004-01-22 1:41 ` [Alsa-user] " Dan Hollis
2004-01-22 11:32 ` Andreas Kuckartz
2004-01-23 2:45 ` Re: [Alsa-devel] " Sam Vilain
2004-01-23 9:59 ` Andreas Kuckartz [this message]
2004-01-21 11:03 ` Takashi Iwai
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='012b01c3e198$4ccb0d00$a501a8c0@computer2' \
--to=a.kuckartz@ping.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=sam@vilain.net \
/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.