From: David Bremner <david@tethera.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: Patch review/application process
Date: Tue, 01 Nov 2011 20:22:58 -0300 [thread overview]
Message-ID: <87ehxr77hp.fsf@zancas.localnet> (raw)
In-Reply-To: <87ehxr4jom.fsf@servo.finestructure.net>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Tue, 01 Nov 2011 14:27:53 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> I'm not sure why this is needed, since it seems to me that the whole
> argument for tagging entire threads is that the individual messages are
> *not* distinguishable from the thread.
The problem is that "notmuch search foo and not bar" will return all
threads containing a message satisfying "foo" and a message satisfying
"not bar". This makes
notmuch search tag:notmuch::patch and not notmuch::pushed
notmuch use.
> Please do *not* remove the ::patch tag.
No, I don't suggest/intend to remove the ::patch tag, only a ::unresolved tag,
since there seems to be no nice way to search for (not notmuch::resolved).
> The addition of something
> From a set of "resolution" tags (::pushed, ::applied, ::obsolete,
> ::rejected, etc.) should indicate resolution of the issue.
Here I think we agree.
[-- Attachment #2: Type: application/pgp-signature, Size: 315 bytes --]
next prev parent reply other threads:[~2011-11-01 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 20:42 Patch review/application process Daniel Schoepe
2011-10-25 23:16 ` David Bremner
2011-10-26 18:29 ` Jani Nikula
2011-10-26 18:55 ` Daniel Schoepe
2011-11-01 14:28 ` David Bremner
2011-11-01 15:55 ` Jameson Graef Rollins
2011-11-01 19:55 ` David Bremner
2011-11-01 21:27 ` Jameson Graef Rollins
2011-11-01 23:22 ` David Bremner [this message]
2011-11-01 23:43 ` Jameson Graef Rollins
2011-11-02 15:49 ` Philip Hands
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=87ehxr77hp.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=jrollins@finestructure.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).