From: "Andreas Kuckartz" <A.Kuckartz@ping.de>
To: alsa-user@lists.sourceforge.net, <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-user] Re: Bugtracking system
Date: 22 Jan 2004 12:32:08 +0100 [thread overview]
Message-ID: <013e01c3e0db$5eb3d7d0$a501a8c0@computer2> (raw)
In-Reply-To: 01dc01c3e019$da571450$a501a8c0@computer2
> In case the proposal is accepted and nobody has connections to the
> maintainers of kernel.org I would volunteer to ask the bugzilla.kernel.org
> maintainer to add a new Category "Sound" with a small number of Components
> (suggestions?).
I have asked the maintainer of bugzilla.kernel.org and he suggested that
ALSA could be treated as an alternate tree within their system. If there are
no counterproposals until this weekend (for example volunteers to setup and
maintain Mantis :-) I will ask him to add this to bugzilla.kernel.org:
Category: "ALSA" (or something similar such as "ALSA (Alternate Tree)" or
"Alternate Tree/ALSA")
Components: "Drivers", "Library", "Tools And Utilities", "Miscellaneous"
As far as I see it new entries should automatically be assigned to the ALSA
developer list.
Comments?/Further suggestions?
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-22 11:32 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 [this message]
2004-01-23 2:45 ` Re: [Alsa-devel] " Sam Vilain
2004-01-23 9:59 ` [Alsa-user] " Andreas Kuckartz
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='013e01c3e0db$5eb3d7d0$a501a8c0@computer2' \
--to=a.kuckartz@ping.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.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.