Linux Documentation
 help / color / mirror / Atom feed
From: Markus Heiser <markus.heiser@darmarit.de>
To: Alex <awaitingvictory@gmail.com>, paulmck@linux.vnet.ibm.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	trivial@kernel.org, Aaron A Montoya <aaron.a.montoya@gmail.com>
Subject: Re: [PATCH] linux: README: reduced README size by 1 byte by removing unnecessary space character
Date: Fri, 7 Jun 2019 19:43:21 +0200	[thread overview]
Message-ID: <d210b4ec-eacf-b521-9e9b-e3d61a70a5fa@darmarit.de> (raw)
In-Reply-To: <20190607055917.17040-1-awaitingvictory@gmail.com>


Am 07.06.19 um 07:59 schrieb Alex:
> From: Aaron A Montoya <aaron.a.montoya@gmail.com>
> 
> On line 9 of the README there is an unnecessary extra space character,
> after the period, that adds 1 byte of size to the file. By removing the
> unnecessary space, Linux downloads will be 1 byte smaller and therefor be
> faster to download and take up less space on a user's system, all while
> correcting a sentence structure issue. This change is one of the few
> optimizations with practically no downsides, besides taking time out
> of the hardworking Linux maintainers day to implement the change.
> Remove extra space after the period on line 9 of the README.
> Commit 0619770a02a30834 ("Removed unnecessary space character from README")
> 

best joke today but wrong in two ways ;)

1. size matter? The commit (-message) adds to more bytes to the repo ;)
2. Be correct formated?  The extra Space is for 'sentence spacing' [1]
    e.g. emacs text modes are formating such spacing.

[1] https://en.wikipedia.org/wiki/Sentence_spacing

-- Markus --

      reply	other threads:[~2019-06-07 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07  5:59 [PATCH] linux: README: reduced README size by 1 byte by removing unnecessary space character Alex
2019-06-07 17:43 ` Markus Heiser [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=d210b4ec-eacf-b521-9e9b-e3d61a70a5fa@darmarit.de \
    --to=markus.heiser@darmarit.de \
    --cc=aaron.a.montoya@gmail.com \
    --cc=awaitingvictory@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=trivial@kernel.org \
    /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