All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Ospite <ao2@ao2.it>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Justin Xu <justinx@slimlogic.co.uk>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [alsa-utils] alsaucm should come with a man page
Date: Mon, 8 Aug 2016 18:30:41 +0200	[thread overview]
Message-ID: <20160808183041.783253de1e523d05bb529760@ao2.it> (raw)
In-Reply-To: <s5hmvkt975u.wl-tiwai@suse.de>

On Wed, 03 Aug 2016 17:57:49 +0200
Takashi Iwai <tiwai@suse.de> wrote:

> On Wed, 27 Jul 2016 11:48:28 +0200,
> Antonio Ospite wrote:
> > 
> > Hi,
> > 
> > I used alsaucm to test mixer use cases for an Intel Baytrail tablet, I
> > wanted to use bare alsa before bringing pulseaudio in, and it took some
> > time to get my head around it.
[...]
> > However, my point is that a man page explaining these things can make
> > the life easier to new users.
> > 
> > It would be better if alsa/UCM developers wrote the man page, but if no
> > one steps up I guess I could draft a first version myself.
> 
> Go ahead, please post your draft version.  That's already helpful.
> 

OK, I will.

The first version will be in a readable text format (maybe asciidoc),
this makes writing and reviewing the content a lot easier.

Then, if depending on an external tool to generate the man page
automatically is not acceptable for alsa-utils, I will format the
approved content manually following the style used in the man pages of
the other alsa programs.

Thanks,
   Antonio

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

  reply	other threads:[~2016-08-08 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  9:48 [alsa-utils] alsaucm should come with a man page Antonio Ospite
2016-08-03 15:57 ` Takashi Iwai
2016-08-08 16:30   ` Antonio Ospite [this message]
2016-09-23 16:37     ` Antonio Ospite
2016-09-29  8:00       ` Takashi Iwai
2016-10-26 17:01         ` Antonio Ospite
2016-12-02 12:11           ` Antonio Ospite
2016-12-02 12:59             ` Liam Girdwood
2016-12-02 13:23               ` Takashi Iwai
2016-12-02 13:47                 ` Antonio Ospite

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=20160808183041.783253de1e523d05bb529760@ao2.it \
    --to=ao2@ao2.it \
    --cc=alsa-devel@alsa-project.org \
    --cc=justinx@slimlogic.co.uk \
    --cc=lrg@slimlogic.co.uk \
    --cc=pierre-louis.bossart@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.