Skip to contentSkip to conversation

utils/readme.txt: fix typos for size-stats-compare

PATCH New Thomas De Schampheleire 3 participants 4 messages Jul 1, 2017 – Jul 2, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 utils/readme.txt: fix typos for size-stats-compare

A few typos sneaked into the new utils readme...

Additionally, I formulated the list of use cases a bit differently.

---
 utils/readme.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
utils/readme.txt +3 -3
index a90805fb0..fd20e8ee6 100644
@@ -28,10 +28,10 @@ scanpypi
     a script to create a Buildroot package by scanning a PyPI package
     description.
 
-size-stat-compare
-    a script to compare the rootfs size between two differnt Buildroot
+size-stats-compare
+    a script to compare the rootfs size between two different Buildroot
     configurations. This can be used to identify the size impact of
-    a specific option, or of a set of specific options, or an update
+    a specific option, of a set of specific options, or of an update
     to a newer Buildroot version...
 
 test-pkg
Signature · 1 line
2.13.0
#1 lore raw

PATCH 1/1 utils/readme.txt: fix typos for size-stats-compare

Thomas, All,

On 2017-07-01 20:00 +0200, Thomas De Schampheleire spake thusly:

Quoted 1 line

A few typos sneaked into the new utils readme...

Yup, sorry...

Quoted 12 lines

Additionally, I formulated the list of use cases a bit differently.

---
 utils/readme.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
utils/readme.txt +0 -0
index a90805fb0..fd20e8ee6 100644

utils/readme.txt scanpypi · line 34

Quoted 10 lines
utils/readme.txt +3 -3
@@ -28,10 +28,10 @@ scanpypi
     a script to create a Buildroot package by scanning a PyPI package
     description.
 
-size-stat-compare
-    a script to compare the rootfs size between two differnt Buildroot
+size-stats-compare
+    a script to compare the rootfs size between two different Buildroot
     configurations. This can be used to identify the size impact of
-    a specific option, or of a set of specific options, or an update
+    a specific option, of a set of specific options, or of an update

I still believe the current situation is prefereable, because it is :

the impact of
- a specific option, or of a set of options,
or
- a new buildroot version

(use of the Oxford comma is very important, here! ;-] )

But yours is not completely incorrect either. ;-)

Regards,
Yann E. MORIN.

Quoted 6 lines
utils/readme.txt +0 -0
     to a newer Buildroot version...
 
 test-pkg
Signature · 1 line
2.13.0
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
#2 lore raw

PATCH 1/1 utils/readme.txt: fix typos for size-stats-compare

Quoted 32 lines · Yann E. MORIN

Thomas, All,

On 2017-07-01 20:00 +0200, Thomas De Schampheleire spake thusly:

Quoted 1 line

A few typos sneaked into the new utils readme...

Yup, sorry...

Quoted 12 lines

Additionally, I formulated the list of use cases a bit differently.

---
 utils/readme.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
utils/readme.txt +0 -0
index a90805fb0..fd20e8ee6 100644

utils/readme.txt scanpypi · line 34

Quoted 10 lines
utils/readme.txt +3 -3
@@ -28,10 +28,10 @@ scanpypi
     a script to create a Buildroot package by scanning a PyPI package
     description.
 
-size-stat-compare
-    a script to compare the rootfs size between two differnt Buildroot
+size-stats-compare
+    a script to compare the rootfs size between two different Buildroot
     configurations. This can be used to identify the size impact of
-    a specific option, or of a set of specific options, or an update
+    a specific option, of a set of specific options, or of an update

I still believe the current situation is prefereable, because it is :

Quoted 6 lines

the impact of
- a specific option, or of a set of options,
or
- a new buildroot version

(use of the Oxford comma is very important, here! ;-] )

Just to make sure we settle this ;-)
The way I see it, the expanded version would be:

... the impact of a specific option, the impact of a set of options, or the impact of a new buildroot version.

which I would shorten to either of:

... the impact of a specific option, a set of options, or a new buildroot version.

... the impact of a specific option or set of options, or of a new buildroot version.

and perhaps other variants, but I feel that _if_ you repeat 'of' in the 'of a set of options' part, then you must also repeat it in the 'new buildroot version' part.

Anyway, who reads these readme's anyway? ;-)

/Thomas

#3 lore raw

PATCH 1/1 utils/readme.txt: fix typos for size-stats-compare

In reply to Thomas De Schampheleire

Hello,

Quoted 8 lines · Thomas De Schampheleire

A few typos sneaked into the new utils readme...

Additionally, I formulated the list of use cases a bit differently.

---
 utils/readme.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Applied to master, thanks.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com