From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 1/2] doc: clean up boolean vs. probabilistic prefixes
Date: Tue, 07 Jun 2016 08:03:26 -0300 [thread overview]
Message-ID: <87mvmx9s75.fsf@zancas.localnet> (raw)
In-Reply-To: <1464883288-19823-1-git-send-email-dkg@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> sphinx-build emits a minor warning:
>
> [...]doc/man7/notmuch-search-terms.rst:223: WARNING: Block quote ends without a blank line; unexpected unindent.
>
pushed, with some spurious whitespace amended away.
d
prev parent reply other threads:[~2016-06-07 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 16:01 [PATCH 1/2] doc: clean up boolean vs. probabilistic prefixes Daniel Kahn Gillmor
2016-06-02 16:01 ` [PATCH 2/2] doc: include nomtuch-emacs-mua in documentation ToC Daniel Kahn Gillmor
2016-06-05 11:40 ` David Bremner
2016-06-07 11:03 ` David Bremner [this message]
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=87mvmx9s75.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=dkg@fifthhorseman.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).