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: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [Fwd: Re: [Jackit-devel] OSS Backend]
Date: Thu, 15 May 2003 10:58:48 +0200	[thread overview]
Message-ID: <s5h3cjgfuwn.wl@alsa2.suse.de> (raw)
In-Reply-To: <3EC32EA5.9040108@boosthardware.com>

At Thu, 15 May 2003 15:07:33 +0900,
Patrick Shirkey wrote:
> 
> [1  <text/plain; us-ascii (7bit)>]
> Before I do this do you think it will be useful or used?
> 
> Specifically Jaroslav and Takashi....
> 
> [2 Re: [Jackit-devel] OSS Backend <message/rfc822 (7bit)>]
> To: Nathaniel Gray <n8gray@caltech.edu>
> CC: jackit-devel@lists.sourceforge.net
> Subject: Re: [Jackit-devel] OSS Backend
> From: Patrick Shirkey <pshirkey@boosthardware.com>
> Message-ID: <3EC32AE8.8070504@boosthardware.com>
> Date: Thu, 15 May 2003 14:51:36 +0900
> Organization: Boost Hardware
> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1)
>  Gecko/20020826
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> 
> Nathaniel Gray wrote:
> > 
> > I would agree if the ALSA drivers were more reliable, but from what I've 
> > seen that's not always the case.  The ALSA developers seem to have 
> > their hands full, bug reports are not handled in any kind of organized 
> > way and are thus regularly dropped.  
> >
> 
> Maybe that should be my next addition to the ALSA website. I get a lot 
> of bug reports through the docs page and it makes sense to reuse that 
> code for a bug reporting system.
> 
> Maybe it will have more psychological impact if it is hosted by ALSA 
> instead of sf.net (which seems to always have something wrong with it 
> anyway).

it would be really appreciated.
i personally dislike the current sf's bug-reporting system.


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  9:07 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 [this message]
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
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=s5h3cjgfuwn.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --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