From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [ANNOUNCE] public-inbox 1.0.0
Date: Thu, 8 Feb 2018 02:33:57 +0000 [thread overview]
Message-ID: <20180208023357.GA32591@80x24.org> (raw)
After some 3.5 odd years of working on this, I suppose now is
as good a time as any to tar this up and call it 1.0.0.
The TODO list is still very long and there'll be some new
development in coming weeks :>
So, here you have a release:
https://public-inbox.org/releases/public-inbox-1.0.0.tar.gz
Checksums, mainly as a safeguard against accidental file corruption:
SHA-256 4a08569f3d99310f713bb32bec0aa4819d6b41871e0421ec4eec0657a5582216
(in other words, don't trust me; instead read the code :>)
reply other threads:[~2018-02-08 2:33 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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180208023357.GA32591@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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).