Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: Jaroslav Kysela <perex@suse.cz>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Re: bug tracking?
Date: Thu, 15 May 2003 14:53:05 +0200	[thread overview]
Message-ID: <s5hy918e5hq.wl@alsa2.suse.de> (raw)
In-Reply-To: <3EC3680A.60904@boosthardware.com>

At Thu, 15 May 2003 19:12:26 +0900,
Patrick Shirkey wrote:
> > - no template for necessary information
> > 
> >   e.g. alsa version, driver, chip/board name/model, output of lspci
> >        output of proc files, etc.
> > 
> 
> These could easily be found with a simple script or maybe there couold 
> be an alsa.debug file in /proc/asound.

yes, a script would be nice.

> > 
> > also, a moderator person would be helpful in addition to the automatic
> > assignment according to the given driver/function.
> > 
> 
> How about having a bugs mailing list and also the address of the driver 
> writer. We could then post the report to the mailing list, the driver 
> writer and also archive it on the alsa website.

the system like bugzilla can communicate via e-mails, too.

> I will start making a bugs page over the next few days which we can fine 
> tune here. I'm not sure that bugzilla is appropriate for ALSA as we have 
> so many different devices to look after however I will use it as a 
> reference.

i'm familiar with bugzilla (not as an adamin but as a user :) and am
satisfied almost with it.  it's enough powerful.
but bugzilla has many configurations and we'll need to find out the
fitting one for our purpose.


Takashi


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

  reply	other threads:[~2003-05-15 13:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  6:07 [Fwd: Re: [Jackit-devel] OSS Backend] Patrick Shirkey
2003-05-15  8:58 ` Takashi Iwai
2003-05-15  9:21   ` bug tracking? Jaroslav Kysela
2003-05-15  9:37     ` Takashi Iwai
2003-05-15 10:12       ` Patrick Shirkey
2003-05-15 12:53         ` Takashi Iwai [this message]
2003-05-20  2:01           ` Patrick Shirkey
2003-05-20 11:34             ` James Courtier-Dutton
2003-05-20 13:25               ` Patrick Shirkey
2003-05-20 14:11             ` Takashi Iwai
2003-05-20 14:51               ` Erik Inge Bolsø
2003-05-20 16:16                 ` Patrick Shirkey
2003-05-20 16:46                 ` Paul Davis
2003-05-20 16:02               ` Patrick Shirkey

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=s5hy918e5hq.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    --cc=pshirkey@boosthardware.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