From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain/wrapper: add option to print one argument per line
Date: Mon, 23 Sep 2013 09:34:54 +0200 [thread overview]
Message-ID: <87mwn49ejl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <31f4ddb9ea718e4bb9321ffb8bf5d75f5fb02361.1379714259.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sat, 21 Sep 2013 00:00:30 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Yann> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Yann> In case there are many arguments passed to the tools, the command line
Yann> can get very long, and difficult to parse visually.
Yann> For example, the Linux kernel passes a lot of arguments to gcc (at least
Yann> 45, which gives 53 with our hard-coded args). Looking at such a command
Yann> line is daunting.
Yann> So, add the possibility to print each argument on its own line.
Yann> Also, enclose all args between single quotes, so the command line
Yann> can be safely copy-pasted without special chars (spaces, $) being
Yann> inrerpreted by the shell.
Yann> Add blurb about toolchain-wrapper to documentation at the same
Yann> time.
Committed with minor code style changes, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-09-23 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 22:00 [Buildroot] [pull request] Pull request for branch yem/misc-updates Yann E. MORIN
2013-09-20 22:00 ` [Buildroot] [PATCH 1/2] toolchain/wrapper: add option to print one argument per line Yann E. MORIN
2013-09-22 8:40 ` Samuel Martin
2013-09-23 7:34 ` Peter Korsgaard [this message]
2013-09-20 22:00 ` [Buildroot] [PATCH 2/2] package/rpi-firmware: bump version Yann E. MORIN
2013-09-23 7:34 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-09-05 18:24 [Buildroot] [PATCH 1/2] toolchain/wrapper: add option to print one argument per line Yann E. MORIN
2013-09-05 18:51 ` Thomas De Schampheleire
2013-09-06 9:39 ` Yann E. MORIN
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=87mwn49ejl.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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