From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] lib: centralize query parsing, store results.
Date: Sat, 04 Mar 2017 22:06:53 -0400 [thread overview]
Message-ID: <87shms8ojm.fsf@tethera.net> (raw)
In-Reply-To: <20170304015356.3684-2-david@tethera.net>
David Bremner <david@tethera.net> writes:
> The main goal is to prepare the way for non-destructive (or at least
> less destructive) exclude tag handling. It does this by having a
> pre-parsed query available for further processing. This also allows us
> to provide slightly more precise errorr messages.
series pushed to master, with the spelling errorr fixed.
d
next prev parent reply other threads:[~2017-03-05 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 1:53 v6 of nondestructive excludes David Bremner
2017-03-04 1:53 ` [PATCH 1/2] lib: centralize query parsing, store results David Bremner
2017-03-05 2:06 ` David Bremner [this message]
2017-03-04 1:53 ` [PATCH 2/2] lib: query make exclude handling non-destructive 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=87shms8ojm.fsf@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).