From: Alex <awaitingvictory@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
trivial@kernel.org, Alex <awaitingvictory@gmail.com>,
Aaron A Montoya <aaron.a.montoya@gmail.com>
Subject: [PATCH] linux: README: reduced README size by 1 byte by removing unnecessary space character
Date: Fri, 7 Jun 2019 01:59:18 -0400 [thread overview]
Message-ID: <20190607055917.17040-1-awaitingvictory@gmail.com> (raw)
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")
Signed-off-by: Aaron A Montoya <aaron.a.montoya@gmail.com>
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 669ac7c32292..0b05d700637f 100644
--- a/README
+++ b/README
@@ -6,7 +6,7 @@ be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
-``make pdfdocs``. The formatted documentation can also be read online at:
+``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
--
2.21.0.windows.1
next reply other threads:[~2019-06-07 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 5:59 Alex [this message]
2019-06-07 17:43 ` [PATCH] linux: README: reduced README size by 1 byte by removing unnecessary space character Markus Heiser
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=20190607055917.17040-1-awaitingvictory@gmail.com \
--to=awaitingvictory@gmail.com \
--cc=aaron.a.montoya@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