Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] crec: Correct name of output binary to crec
Date: Fri, 18 Nov 2016 15:55:51 +0530	[thread overview]
Message-ID: <20161118102551.GR2698@localhost> (raw)
In-Reply-To: <1479463990.18450.31.camel@rf-debian.wolfsonmicro.main>

On Fri, Nov 18, 2016 at 10:13:10AM +0000, Richard Fitzgerald wrote:
> > This part I agree. Unfortunately this was not done transparently...
> > 
> > > b) the source file should have been renamed to match, if the name "crec"
> > > is a massive problem then it should also be a problem that
> > > "cplay.c->cplay" but "crec.c->crecord". If it's ok to have the source
> > > file called crec.c what's wrong with the binary it builds being called
> > > crec?
> > 
> > I dont mind renaming source as well..
> > 
> > I think bigger question is should we continue crec or crecord, my preference
> > is latter.
> > 
> > > c) it's a nuisance to have to change existing test systems and apps that
> > > launch "crec", or to create symlinks from crec->crecord.
> > 
> > Yeah agree, lets decide on one and stick to that, forever hopefully :)
> > 
> 
> Ok let's change to crecord for consistency with arecord, and I'll do a
> patch to rename the source to match.

Sounds good :)

-- 
~Vinod

      reply	other threads:[~2016-11-18 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 11:06 [PATCH] crec: Correct name of output binary to crec Richard Fitzgerald
2016-11-16 13:02 ` Vinod Koul
2016-11-16 13:14   ` Richard Fitzgerald
2016-11-18  3:56     ` Vinod Koul
2016-11-18 10:13       ` Richard Fitzgerald
2016-11-18 10:25         ` Vinod Koul [this message]

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=20161118102551.GR2698@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=rf@opensource.wolfsonmicro.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