On Fri, 2016-03-04 at 18:03 +0100, Takashi Iwai wrote: > On Fri, 04 Mar 2016 09:14:52 +0100, > Tanu Kaskinen wrote: > > > > Hi, > > > > When talking with PulseAudio users, I sometimes need to tell people to > > file ALSA bugs, and it would be nice to have a web page that explains > > how to do that. (Also, I found that the alsa packages in OpenEmbedded > > point to a non-functional bug tracker, and I wanted to fix the > > packages, but I couldn't find a substitute link.) Therefore I created a > > wiki page: http://alsa-project.org/main/index.php/Bug_Tracking > > > > The Bug_Tracking wiki page points to another new page, explaining alsa- > > info.sh: http://alsa-project.org/main/index.php/AlsaInfo > > > > Are the ALSA maintainers happy with the contents? I'm not really an > > expert on how you prefer bugs to be reported. > > Yeah, I'm happy with it. Thank you! > > Though, a few more hints would be better to be put: > - alsa-devel ML needs the manual approval if posted from > non-subscribers. Subscribe to ML before posting, or be patient. > > - A too long text is seen as a spam. The alsa-info.sh output might be > better compressed and attached to the mail. (A long text can go out > after the manual approval, though.) > > - HTML mails are silently dropped as spam on alsa-devel ML. Thanks, I added these points to the wiki page now. -- Tanu _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
