From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Subject: Cleaned up homepage, regenerated manual, added release script
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <e9e0edee8a6c2bf9f4ddbe8ffc06207e8c092932.camel@klomp.org> (raw)
Hi,
I have cleaned up the homepage a bit by removing all explicit version
references and adding pointers to this mailinglist, bugzilla, git and
the (older) downloads. See the bzip2-htdocs git repo:
https://sourceware.org/git/?p=bzip2-htdocs.git;a=summary
anything committed there will automatically update the homepage:
https://sourceware.org/bzip2/
I regenerated the manual and other artifacts with the latest version.
To make everything look right I had to update the bzip.css for the new
layout (commit ddd8ba) and adjusted bz-html.xsl to make sure we
generate UTF-8 and explicitly include a link to the bzip.css stylesheet
(commit ac9b38).
To make it easy for others to do this whenever we do a new release
there is now a release-update.sh script (commit 32db5b). That uploads
the downloads and updates the webpages. For anybody in the bzip2 group
on sourceware.
Cheers,
Mark
reply other threads:[~2019-06-23 21:37 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=e9e0edee8a6c2bf9f4ddbe8ffc06207e8c092932.camel@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).