public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, Mark Wielaard <mark@klomp.org>
Subject: [bzip2-tests COMMITTTED] README: Change none bad files -> non-bad files.
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <1562004554-15470-1-git-send-email-mark@klomp.org> (raw)

Reported-by: Jonathan Wakely <jwakely.gcc@gmail.com>
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index bbb2995..f684c24 100644
--- a/README
+++ b/README
@@ -12,7 +12,7 @@ corrupt files. They are explicitly not intended to decompress correctly,
 but to catch errors in bzip2 trying to deal with deliberately bad data.
 All such files have a name ending in .bz2.bad.
 
-All none bad files end in bz2. And should come with a .md5 file for
+All non-bad files end in bz2. And should come with a .md5 file for
 the original input file. The .md5 file is used to check that bzip2
 could correctly decompress the file. The original (non-compressed)
 files are deliberately not checked in.
-- 
1.8.3.1

                 reply	other threads:[~2019-07-01 18:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1562004554-15470-1-git-send-email-mark@klomp.org \
    --to=mark@klomp.org \
    --cc=bzip2-devel@sourceware.org \
    --cc=jwakely.gcc@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).