From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] crec: Correct name of output binary to crec
Date: Wed, 16 Nov 2016 13:14:21 +0000 [thread overview]
Message-ID: <1479302061.18450.24.camel@rf-debian.wolfsonmicro.main> (raw)
In-Reply-To: <20161116130241.GY3000@localhost>
On Wed, 2016-11-16 at 18:32 +0530, Vinod Koul wrote:
> On Wed, Nov 16, 2016 at 11:06:45AM +0000, Richard Fitzgerald wrote:
> > For some reason when the build system was converted to
> > automake by this patch
> >
> > "Convert the build system to autotools"
> >
> > the name of the output binary for crec was changed
> > from 'crec' to 'crecord'.
> >
> > This patch corrects it back to 'crec'
>
> That implies crecord is incorrect, I do not think so.
>
> Can you explain why you would want to rename this back.
>
> The motivation for this was to make it proper like cplay. Also similar to
> aplay and arecord.
>
I don't really see a need for that, or why "crec" is wrong.
In any case if you did want to change that name
a) it should be an explicit patch, not sneaked in as an undocumented and
unexpected side-effect of some other patch
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?
c) it's a nuisance to have to change existing test systems and apps that
launch "crec", or to create symlinks from crec->crecord.
next prev parent reply other threads:[~2016-11-16 13:14 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 [this message]
2016-11-18 3:56 ` Vinod Koul
2016-11-18 10:13 ` Richard Fitzgerald
2016-11-18 10:25 ` Vinod Koul
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=1479302061.18450.24.camel@rf-debian.wolfsonmicro.main \
--to=rf@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).