Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	adconrad@0c3.net, luke.yelavich@canonical.com
Subject: Re: Alsa-info.sh is never released
Date: Tue, 22 Jul 2014 08:28:10 +0200	[thread overview]
Message-ID: <53CE047A.7000909@canonical.com> (raw)
In-Reply-To: <s5hwqb5hq1j.wl%tiwai@suse.de>



On 2014-07-22 08:21, Takashi Iwai wrote:
> At Tue, 22 Jul 2014 08:03:34 +0200,
> David Henningsson wrote:
>>
>> Hi,
>>
>> Since ~two years back Ubuntu ships alsa-info.sh on new installations, in
>> order to have bug reports that are upstream compatible.
>>
>> However, alsa-info.sh seems to be a part of the alsa-driver git tree,
>> and the alsa-driver package is not released anymore, since we think that
>> is a part of the Linux kernel. As a result, alsa-info.sh is no longer
>> part of an upstream tarball that we can package in the usual way.
>>
>> So maybe we should move alsa-info somewhere else, e g alsa-utils? What
>> do you think?
>
> +1.  alsa-utils or alsa-tools is a better place to maintain.

I'd prefer alsa-utils over alsa-tools: alsa-utils seems to have generic 
utilities and alsa-tools specialised ones (i e for some specific 
hardware). Since alsa-info is a generic tool (usable for everyone, 
regardless of driver/hardware), alsa-utils seems to be a better fit.


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  reply	other threads:[~2014-07-22  6:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  6:03 Alsa-info.sh is never released David Henningsson
2014-07-22  6:21 ` Takashi Iwai
2014-07-22  6:28   ` David Henningsson [this message]
2014-08-04 13:24     ` 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=53CE047A.7000909@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=adconrad@0c3.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=luke.yelavich@canonical.com \
    --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