From: David Bremner <david@tethera.net>
To: notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: release plan for 0.17
Date: Sat, 30 Nov 2013 09:21:06 -0400 [thread overview]
Message-ID: <87r49y3u0t.fsf@zancas.localnet> (raw)
In-Reply-To: <87iovi7esa.fsf@zancas.localnet>
I have pushed a tag 0.17_rc2 which has a couple of bug fixes from
0.17_rc1. Unless some serious bug turns up I'd like to release 0.17
next week. People are encouraged to look at
git shortlog 0.16..0.17_rc2
and look for missing NEWS items. My (subjectively) edited version
follows. (P.S. congrats to Mark Walters, who moves in to #4 in the
overall commit race, #1 for this release ;) )
----------------------------------------------------------------------
Blake Jones (4):
getpwuid: check for standards compliance (Solaris support)
strsep: check for availability (Solaris support)
timegm: add portable implementation (Solaris support)
notmuch-config: use strchr(), not index() (Solaris support)
Charlie Allom (1):
vim: run mutt in default term
Gregor Zattler (1):
emacs: distinguish tag `flagged' on terminal
Istvan Marko (1):
emacs: add buttons for all multipart/related parts
John Lenz (1):
cli: add --include-html option to notmuch show
Kevin J. McCarthy (2):
notmuch-mutt: Fix tagging issues
notmuch-mutt: use notmuch --duplicate flag
Louis Rilling (1):
tags_to_maildir_flags: Don't rename if no flags change
Mark Walters (66):
emacs: show: lazy part handling bugfix
emacs: bugfix unquoted symbol
emacs: do not put quoted reply in primary selection
emacs: show: stop stderr appearing in buffer
next prev parent reply other threads:[~2013-11-30 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 12:51 release plan for 0.17 David Bremner
2013-11-24 1:46 ` David Bremner
2013-11-30 13:21 ` David Bremner [this message]
2013-11-30 13:53 ` [PATCH] News updates for Mark's bugfixes Mark Walters
2013-12-01 20:57 ` David Bremner
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=87r49y3u0t.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).