From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Andre Przywara <osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
Cc: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/3] allow a second parameter to be the output file name
Date: Tue, 30 Jun 2015 15:11:19 +1000 [thread overview]
Message-ID: <20150630051119.GK26353@voom.redhat.com> (raw)
In-Reply-To: <1432595483-26153-4-git-send-email-osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
On Tue, May 26, 2015 at 12:11:23AM +0100, Andre Przywara wrote:
> If there is more than one file name specified on the command line,
> assume it is the output file name.
> This allows to use a more intuitive cp-style command line syntax,
> which (together with the input type guessing) allows something like:
> $ dtc input.dts output.dtb
> (or the other way round) to cover the most common usage scenarios.
>
> Signed-off-by: Andre Przywara <osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
Nack to this, sorry.
I'd prefer to model our command line on other compilers, and -o is a
more common convention there.
I would however, accept a patch to guess an output name based on input
name if -o is not specified, allowing the output name to be omitted
entirely in common cases.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-30 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 23:11 [PATCH 0/3] dtc: simplify command line invocation Andre Przywara
[not found] ` <1432595483-26153-1-git-send-email-osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
2015-05-25 23:11 ` [PATCH 1/3] guess input file format based on file content or file name Andre Przywara
[not found] ` <1432595483-26153-2-git-send-email-osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
2015-06-30 5:07 ` David Gibson
[not found] ` <20150630050749.GJ26353-1s0os16eZneny3qCrzbmXA@public.gmane.org>
2015-06-30 23:21 ` Andre Przywara
2015-05-25 23:11 ` [PATCH 2/3] guess output file format Andre Przywara
2015-05-25 23:11 ` [PATCH 3/3] allow a second parameter to be the output file name Andre Przywara
[not found] ` <1432595483-26153-4-git-send-email-osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
2015-06-30 5:11 ` David Gibson [this message]
[not found] ` <20150630051119.GK26353-1s0os16eZneny3qCrzbmXA@public.gmane.org>
2015-06-30 23:15 ` Andre Przywara
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=20150630051119.GK26353@voom.redhat.com \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.org \
--cc=osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org \
/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).