unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: bug fix release 0.22.1
Date: Wed, 29 Jun 2016 20:29:42 +0200	[thread overview]
Message-ID: <8737nv26i1.fsf@maritornes.cs.unb.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]


Hi Team;

A long time ago, David E. fixed a couple of annoying bugs with the emacs
interface, and I added two commits to the release branch with the intent
of making a bugfix point release. Then I got distracted, and never made
that release.  Are there any other small, but important fixes in master
that I should cherrypick? A few candidates are listed below.

David Bremner:
      lib: fix definition of LIBNOTMUCH_CHECK_VERSION
      - this is a pretty embarrassing bug
      
      doc: forbid further operations on a closed database
      - this is not so important, but would let me close a debian
      bug ;)
      
      test: don't use dump and restore in a pipeline
      - these seems like a test failing in the waiting.
      
Mark Walters:
      emacs: show: improve handling of mark read tagging errors
      - not sure if this really fits the small bugfix category.
            
Stefano Zacchiroli:
      notmuch-mutt: use env to locate perl for increased portability
      - I don't use notmuch mutt, but it's a small fix
      
Tomi Ollila:
      test: set LD_LIBRARY_PATH early and keep its old contents
      - this seems like it could be annoying

      test: test_python: set PYTHONPATH to the python execution environment
      - I'm less sure about this one


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 647 bytes --]

             reply	other threads:[~2016-06-29 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 18:29 David Bremner [this message]
2016-06-29 18:57 ` bug fix release 0.22.1 Tomi Ollila
2016-06-30  5:51   ` Mark Walters
2016-06-30 20:21     ` 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=8737nv26i1.fsf@maritornes.cs.unb.ca \
    --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).