public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Add bzip2-test to downloads.
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <1562005217-27716-1-git-send-email-mark@klomp.org> (raw)

Explain how to get the bzip2 test suite.

---
 downloads.html | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/downloads.html b/downloads.html
index bab004d..deef6c2 100644
--- a/downloads.html
+++ b/downloads.html
@@ -32,7 +32,7 @@
 
 <h1>Downloads</h1>
 
-<h2>Classic bzip2 1.0.x</h2>
+<h3>Classic bzip2 1.0.x</h3>
 
 <p>Here is the <a href="/pub/bzip2/bzip2-latest.tar.gz">latest bzip2 1.0.x
 source tarball</a> release, which includes full documentation.</p>
@@ -45,7 +45,14 @@ or
 <p>The bzip2 1.0.x <a href="https://sourceware.org/git/?p=bzip2.git;a=summary">git tree</a> can be checked out with:</p>
 <p><div><tt>git clone git://sourceware.org/git/bzip2.git</tt></div><p>
 
-<h2>Modern bzip2 1.1.x</h2>
+<h3>bzip2 test suite</h3>
+
+<p>The bzip2 test suite is maintained in a seperate repository and contains
+test files from various bzip2 implementations to check compatibility. It can
+be checked out with:</p>
+<p><div><tt>git clone git://sourceware.org/git/bzip2-tests.git</tt></div><p>
+
+<h3>Modern bzip2 1.1.x</h3>
 <p>There is also a future <a href="https://gitlab.com/federicomenaquintero/bzip2">bzip2 1.1.x development branch</a> which includes a new build system and more fixes.</p>
 
 <p>If you can be bothered, please 
-- 
1.8.3.1

                 reply	other threads:[~2019-07-01 18:20 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=1562005217-27716-1-git-send-email-mark@klomp.org \
    --to=mark@klomp.org \
    --cc=bzip2-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).