From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] gdb texinfo dependency
Date: Fri, 7 Oct 2016 22:19:31 +0200 [thread overview]
Message-ID: <20161007221931.28362f04@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LXRG2My5hyc19CS+LBm3dUuopPMDd7EqBkFypGEi_0GmA@mail.gmail.com>
Hello,
On Fri, 7 Oct 2016 21:34:09 +0200, Thomas De Schampheleire wrote:
> I think it is a matter of personal taste.
> The fact that : is a shell built-in means that it's a tad faster than
> spawning a separate 'true' process, but I really think it does not
> matter here.
> 'MAKEINFO=true' has the drawback that it gives the impression of
> _enabling_ makeinfo, to people that are not used to such
> constructions.
> 'MAKEINFO=:' has the drawback that it is cryptic; it is even less
> known to most people (I think).
> So I guess I'll stick to 'true'.
Yes, I also think that using "true" is less cryptic.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-07 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 15:14 [Buildroot] gdb texinfo dependency Thomas De Schampheleire
2016-10-05 15:27 ` Thomas Petazzoni
2016-10-05 20:11 ` Thomas De Schampheleire
2016-10-05 20:16 ` Thomas Petazzoni
2016-10-05 21:23 ` Romain Naour
2016-10-06 18:57 ` Thomas De Schampheleire
2016-10-06 18:59 ` Thomas De Schampheleire
2016-10-06 19:36 ` Thomas Petazzoni
[not found] ` <CAAXf6LUwubkNu9+25LUZyOMchdFfHjYUa5pzdfOF9xYfjzWamA@mail.gmail.com>
[not found] ` <CAAXf6LXcZ2BOc+znu6GQFX3oC=LVAYO=inYGwk83JKHRQR2T-g@mail.gmail.com>
2016-10-06 19:50 ` Thomas De Schampheleire
2016-10-07 12:21 ` Thomas Petazzoni
2016-10-07 16:20 ` Khem Raj
2016-10-07 19:36 ` Thomas De Schampheleire
2016-10-07 20:18 ` Thomas Petazzoni
2016-10-07 19:34 ` Thomas De Schampheleire
2016-10-07 20:19 ` Thomas Petazzoni [this message]
2016-10-05 15:43 ` Khem Raj
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=20161007221931.28362f04@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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