Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] utils/readme.txt: fix typos for size-stats-compare
Date: Sat, 1 Jul 2017 20:21:29 +0200	[thread overview]
Message-ID: <20170701182129.GE3593@scaer> (raw)
In-Reply-To: <20170701180027.GY29444@argentina>

Thomas, All,

On 2017-07-01 20:00 +0200, Thomas De Schampheleire spake thusly:
> A few typos sneaked into the new utils readme...

Yup, sorry...

> Additionally, I formulated the list of use cases a bit differently.
> 
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
>  utils/readme.txt | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/utils/readme.txt b/utils/readme.txt
> index a90805fb0..fd20e8ee6 100644
> --- a/utils/readme.txt
> +++ b/utils/readme.txt
> @@ -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. ;-)

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

>      to a newer Buildroot version...
>  
>  test-pkg
> -- 
> 2.13.0
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-07-01 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 18:00 [Buildroot] [PATCH 1/1] utils/readme.txt: fix typos for size-stats-compare Thomas De Schampheleire
2017-07-01 18:21 ` Yann E. MORIN [this message]
2017-07-02 12:26   ` Thomas De Schampheleire
2017-07-01 22:35 ` 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=20170701182129.GE3593@scaer \
    --to=yann.morin.1998@free.fr \
    --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