From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Last call for 0.23 NEWS
Date: Sat, 01 Oct 2016 10:33:04 -0300 [thread overview]
Message-ID: <87fuogi48f.fsf@zancas.localnet> (raw)
In-Reply-To: <87shsmkh16.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
David Bremner <david@tethera.net> writes:
> We are now frozen for 0.23. I have tagged 0.23_rc0 in git, and uploaded
> it to debian experimental. At this point I expect only NEWS changes and
> serious bug fixes before release.
I have tagged 0.23_rc1 in git (and uploaded to Debian experimental). If
I don't hear of any serious problems before Monday, I'll release that,
along with any last minute NEWS patches as 0.23.
d
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
prev parent reply other threads:[~2016-10-01 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 1:43 freeze for 0.23 David Bremner
2016-09-26 12:00 ` David Bremner
2016-10-01 13:33 ` David Bremner [this message]
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuogi48f.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).