From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Second batch of API cleanup for exception safety.
Date: Sat, 4 Jul 2020 12:17:54 -0300 [thread overview]
Message-ID: <20200704151805.3717715-1-david@tethera.net> (raw)
This is going to be a bit of a slog, so I'm going to send the patches
in batches, rather than waiting until I have one giant series.
I'm interested in feedback on the last two patches in particular
before I adjust notmuch to use the new API itself. An alternative
approach would be treat being a ghost_message as a seperate property
(and leave the old notmuch_bool_t API for the other flags). That seems
harder to migrate to cleanly, but I'm open to ideas.
next reply other threads:[~2020-07-04 15:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 15:17 David Bremner [this message]
2020-07-04 15:17 ` [PATCH 01/11] test: remove unused backup_database calls David Bremner
2020-07-04 15:17 ` [PATCH 02/11] test: drop use of assert in closed db tests David Bremner
2020-07-04 15:17 ` [PATCH 03/11] lib/message: use LOG_XAPIAN_EXCEPTION in n_m_get_header David Bremner
2020-07-04 15:17 ` [PATCH 04/11] test: add regression test for n_m_get_header David Bremner
2020-07-04 15:17 ` [PATCH 05/11] lib/n_m_get_replies: doc return, initial regression test David Bremner
2020-07-04 15:18 ` [PATCH 06/11] lib: add known broken test for notmuch_message_get_filename David Bremner
2020-07-04 15:18 ` [PATCH 07/11] lib/n_m_g_filename: catch Xapian exceptions, document NULL return David Bremner
2020-07-04 15:18 ` [PATCH 08/11] test: add known broken test for n_m_get_filenames David Bremner
2020-07-04 15:18 ` [PATCH 09/11] lib: catch exceptions in n_m_get_filenames David Bremner
2020-07-04 15:18 ` [PATCH 10/11] test: add known broken for n_m_get_flag on closed db David Bremner
2020-07-13 10:37 ` David Bremner
2020-07-04 15:18 ` [PATCH 11/11] lib: catch exceptions in n_m_get_flag, provide n_m_get_flag_st David Bremner
2020-07-18 14:32 ` 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=20200704151805.3717715-1-david@tethera.net \
--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).