From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trivial: fix typo 'informations'
Date: Thu, 24 Jul 2014 20:07:02 +0200 [thread overview]
Message-ID: <37734712403055c8a791.1406225222@localhost> (raw)
In English, unlike in French, almost all usages of the word 'information'
are uncountable, meaning that 'informations' is invalid.
This patch fixes this typo throughout the tree, except in CHANGES and
docs/news.html (historic text).
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
board/minnowboard/readme.txt | 2 +-
package/pkg-autotools.mk | 2 +-
package/pkg-cmake.mk | 2 +-
package/pkg-generic.mk | 4 ++--
package/pkg-luarocks.mk | 2 +-
package/pkg-python.mk | 2 +-
support/scripts/xorg-release | 4 ++--
7 files changed, 9 insertions(+), 9 deletions(-)
diff -r e79d6f3e1d9c -r 377347124030 board/minnowboard/readme.txt
--- a/board/minnowboard/readme.txt Tue Mar 04 14:50:03 2014 +0000
+++ b/board/minnowboard/readme.txt Thu Jul 24 20:01:15 2014 +0200
@@ -36,5 +36,5 @@
4. Enjoy
-Additional informations about this board can be found at
+Additional information about this board can be found at
http://www.minnowboard.org/.
diff -r e79d6f3e1d9c -r 377347124030 package/pkg-autotools.mk
--- a/package/pkg-autotools.mk Tue Mar 04 14:50:03 2014 +0000
+++ b/package/pkg-autotools.mk Thu Jul 24 20:01:15 2014 +0200
@@ -9,7 +9,7 @@
# infrastructure
#
# In terms of implementation, this autotools infrastructure requires
-# the .mk file to only specify metadata informations about the
+# the .mk file to only specify metadata information about the
# package: name, version, download URL, etc.
#
# We still allow the package .mk file to override what the different
diff -r e79d6f3e1d9c -r 377347124030 package/pkg-cmake.mk
--- a/package/pkg-cmake.mk Tue Mar 04 14:50:03 2014 +0000
+++ b/package/pkg-cmake.mk Thu Jul 24 20:01:15 2014 +0200
@@ -9,7 +9,7 @@
# infrastructure
#
# In terms of implementation, this CMake infrastructure requires
-# the .mk file to only specify metadata informations about the
+# the .mk file to only specify metadata information about the
# package: name, version, download URL, etc.
#
# We still allow the package .mk file to override what the different
diff -r e79d6f3e1d9c -r 377347124030 package/pkg-generic.mk
--- a/package/pkg-generic.mk Tue Mar 04 14:50:03 2014 +0000
+++ b/package/pkg-generic.mk Thu Jul 24 20:01:15 2014 +0200
@@ -13,7 +13,7 @@
# In terms of implementation, this generic infrastructure requires the
# .mk file to specify:
#
-# 1. Metadata informations about the package: name, version,
+# 1. Metadata information about the package: name, version,
# download URL, etc.
#
# 2. Description of the commands to be executed to configure, build
@@ -304,7 +304,7 @@
# already defined. For some variables (version, source, site and
# subdir), if they are undefined, we try to see if a variable without
# the HOST_ prefix is defined. If so, we use such a variable, so that
-# these informations have only to be specified once, for both the
+# this information has only to be specified once, for both the
# target and host packages of a given .mk file.
$(2)_TYPE = $(4)
diff -r e79d6f3e1d9c -r 377347124030 package/pkg-luarocks.mk
--- a/package/pkg-luarocks.mk Tue Mar 04 14:50:03 2014 +0000
+++ b/package/pkg-luarocks.mk Thu Jul 24 20:01:15 2014 +0200
@@ -12,7 +12,7 @@
# infrastructure
#
# In terms of implementation, this LuaRocks infrastructure requires
-# the .mk file to only specify metadata informations about the
+# the .mk file to only specify metadata information about the
# package: name, version, etc.
#
################################################################################
diff -r e79d6f3e1d9c -r 377347124030 package/pkg-python.mk
--- a/package/pkg-python.mk Tue Mar 04 14:50:03 2014 +0000
+++ b/package/pkg-python.mk Thu Jul 24 20:01:15 2014 +0200
@@ -9,7 +9,7 @@
# infrastructure
#
# In terms of implementation, this Python infrastructure requires the
-# .mk file to only specify metadata informations about the package:
+# .mk file to only specify metadata information about the package:
# name, version, download URL, etc.
#
# We still allow the package .mk file to override what the different
diff -r e79d6f3e1d9c -r 377347124030 support/scripts/xorg-release
--- a/support/scripts/xorg-release Tue Mar 04 14:50:03 2014 +0000
+++ b/support/scripts/xorg-release Thu Jul 24 20:01:15 2014 +0200
@@ -101,7 +101,7 @@
return m.group(2)
return None
-# Augment the informations of the X.org list of packages (given as
+# Augment the information of the X.org list of packages (given as
# argument) by details about their packaging in Buildroot. Those
# details are found by looking at the contents of package/x11r7/.
def get_buildroot_pkgs(packages):
@@ -114,7 +114,7 @@
version = buildroot_get_version(d)
if packages.has_key(pkgname):
# There is a X.org package of the same name, so we just
- # add informations to the existing dict entry.
+ # add information to the existing dict entry.
packages[pkgname]['br-version'] = version
packages[pkgname]['br-name'] = d
else:
next reply other threads:[~2014-07-24 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 18:07 Thomas De Schampheleire [this message]
2014-07-24 18:12 ` [Buildroot] [PATCH] trivial: fix typo 'informations' Yann E. MORIN
2014-07-24 19:01 ` Thomas De Schampheleire
2014-07-24 20:31 ` Thomas Petazzoni
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=37734712403055c8a791.1406225222@localhost \
--to=patrickdepinguin@gmail.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