Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vedran Miletić" <rivanvx@gmail.com>
To: "A. C. Censi" <accensi@gmail.com>,
	alsa-devel mailing list <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: ALSA bug-tracking
Date: Sat, 1 Nov 2008 10:27:51 +0100	[thread overview]
Message-ID: <fd3eb9bf0811010227l35da0d63w3685559c530d1f48@mail.gmail.com> (raw)
In-Reply-To: <643ea2b10810300723y527196d0mbc6d6ac9800bcd70@mail.gmail.com>

I second this idea.

2008/10/30 A. C. Censi <accensi@gmail.com>:
> On Thu, Oct 30, 2008 at 9:25 AM, Takashi Iwai <tiwai@suse.de> wrote,
> on the reply to this message Re: [alsa-devel] Automatic
> assignment/configuration of model-id?:
>
>> The best way to inform the model addition is to post to alsa-devel
>> ML, and/or post to me or other developers.
>>
>> A bad way is, unfortunately, to submit it on ALSA bug-tracking
>> system.  It's handled right now very badly, and you post would be
>> often ignored.
>
> Why not shut down ALSA bug-tracking, or, at least, put this advice
> there (if not already, i've not checked)?
>
>
> --
> A. C. Censi
> accensi [em] gmail [ponto] com
> accensi [em] montreal [ponto] com [ponto] br
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>



-- 
Vedran Miletić
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-11-01  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 14:23 ALSA bug-tracking A. C. Censi
2008-11-01  9:27 ` Vedran Miletić [this message]
2008-11-01  9:52   ` Takashi Iwai
2008-11-01 10:24     ` Colin Guthrie

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=fd3eb9bf0811010227l35da0d63w3685559c530d1f48@mail.gmail.com \
    --to=rivanvx@gmail.com \
    --cc=accensi@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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