From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: handle NOTMUCH_STATUS_ERROR_MESSAGE
Date: Tue, 29 Mar 2016 23:10:12 -0300 [thread overview]
Message-ID: <1459303814-31988-1-git-send-email-david@tethera.net> (raw)
There's what looks like a race condition discussed at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698810
This doesn't do anything about the race condition, but tries to report
more helpful information when it happens.
If I knew how to test this properly, I'd probably know how to
reproduce the race condition.
The first page in the series is needed for some other things, so it's
not as much overkill as it looks.
next reply other threads:[~2016-03-30 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 2:10 David Bremner [this message]
2016-03-30 2:10 ` [PATCH 1/2] CLI: add print_status_database David Bremner
2016-03-30 20:50 ` Tomi Ollila
2016-03-31 1:34 ` David Bremner
2016-03-30 2:10 ` [PATCH 2/2] cli/new: add better error messages for FILE_ERROR 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=1459303814-31988-1-git-send-email-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).