From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trivial: correct capitalization of Lua in Config.in files
Date: Sat, 7 Sep 2013 12:46:11 +0200 [thread overview]
Message-ID: <20130907124611.30084592@skate> (raw)
In-Reply-To: <37b9a5e957cd96df84ea.1378503378@argentina>
On Fri, 06 Sep 2013 23:36:18 +0200, Thomas De Schampheleire wrote:
> The Lua website says:
> "Like most names, it should be written in lower case with an initial capital,
> that is, "Lua". Please do not write it as "LUA", which is both ugly and
> confusing, because then it becomes an acronym with different meanings for
> different people."
> http://www.lua.org/about.html
>
> So, let's honor this request in buildroot.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-09-07 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 21:36 [Buildroot] [PATCH] trivial: correct capitalization of Lua in Config.in files Thomas De Schampheleire
2013-09-07 6:14 ` Peter Korsgaard
2013-09-07 10:46 ` Thomas Petazzoni [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=20130907124611.30084592@skate \
--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