Re: [PATCH] make release archive: common (or no) timestamps

Tomi Ollila writes: > The appended file 'version' has the same timestamp as the files added > by `git archive`. pushed. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch

Xapian exception leading to database corruption

Using current git notmuch on Debian testing a rebuild from scratch of my database fails: > agrajag-testing ~/s/notmuch % ./notmuch new > Found 605510 total files (that's not much mail). > add_file: A Xapian exception occurred 28m 37s remaining). > A Xapian exception occurred adding message:

[PATCH 1/2] nmbug: Bump to version 0.3

Changes since 0.2: * Accept failures to unset core.worktree in clone (0a155847, 2017-10-10, unreleased). * Use --no-renames in log (f9189a06, 2016-09-26, v0.24). * Auto-checkout in clone if it wouldn't clobber (7ef3b653, 2017-10-10, unreleased). * Add a 'help' command for folks who don't like

Re: Notmuch 0.26 release schedule

David Bremner writes: > I plan a feature freeze for December 25, and a release (all going well) > on or around January 1. I've tagged 0.26_rc0 (and uploaded to Debian experimental). I expect a few more changes before final release, but I want to start to shake out any build

[PATCH 0/2] nmbug: Bump to 0.3 and document in NEWS

As discussed previously in [1,2,3]. I've split this into two patches, and only covered the changes since the last notmuch release. There have been additional changes since nmbug 0.2 (which went out with notmuch 0.19), and I mention them in the commit message for patch 1/1, but none of them

[PATCH 2/2] NEWS: Add nmbug 0.3 release notes to the notmuch 0.26 section

--- NEWS | 13 + 1 file changed, 13 insertions(+) diff --git a/NEWS b/NEWS index 6d2bf138..3b6404e7 100644 --- a/NEWS +++ b/NEWS @@ -41,6 +41,19 @@ Indexing cleartext of encrypted e-mails that the notmuch index itself is adequately protected. DO NOT USE this feature without

Re: [PATCH v4 1/3] cli: some keyword options can be supplied with no argument

On Sat 2017-12-23 10:29:30 -0400, David Bremner wrote: > Daniel Kahn Gillmor writes: > >> >> +bool incremented = false; >> if (next == '\0' && next_arg != NULL && ! try->opt_bool) { >> next = ' '; >> value = next_arg; >> +incremented =

Re: [PATCH v4 2/3] cli/show: make --decrypt take a keyword.

On Sat 2017-12-23 10:39:47 -0400, David Bremner wrote: > One thing that gave me pause is the fact that --decrypt=auto does not > verify by default. What are the security implications of this? The only issue is that some messages that are correctly signed are marked as unsigned if the user hasn't

Re: [PATCH v4 3/3] cli/reply: make --decrypt take a keyword

On Sat 2017-12-23 10:47:52 -0400, David Bremner wrote: > Daniel Kahn Gillmor writes: >> +{ .opt_keyword = (int*)(), .name = "decrypt", >> + .keyword_no_arg_value = "true", .keywords = >> + (notmuch_keyword_t []){ { "false", NOTMUCH_DECRYPT_FALSE }, >> +

Re: Xapian exception leading to database corruption

David Edmondson writes: > Using current git notmuch on Debian testing a rebuild from scratch of my > database fails: > >> agrajag-testing ~/s/notmuch % ./notmuch new >> Found 605510 total files (that's not much mail). >> add_file: A Xapian exception occurred 28m 37s remaining).