From: servilio <servilio@gmail.com>
To: Austin Clements <amdragon@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] add headers cc: bcc: and to: (as exactto:) to search index
Date: Sun, 12 Dec 2010 17:01:55 -0500 [thread overview]
Message-ID: <AANLkTin2ocjB5u=hYBXoSUGw7PdV7HxKOHP4Yd2xHcL_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikDQgpeM-Ari2woxUgwpuAH3VVq-O-vQvOGU-hO@mail.gmail.com>
I think it would be better to leave the To, Cc and Bcc as they are and
just add a "recipient" term, the name is easier to grasp.
Servilio
prev parent reply other threads:[~2010-12-12 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 20:33 [PATCH] add headers cc: bcc: and to: (as exactto:) to search index Joel Borggrén-Franck
2010-12-02 17:48 ` Dirk Hohndel
2010-12-03 5:49 ` Xavier Maillard
2010-12-12 6:41 ` Austin Clements
2010-12-12 10:43 ` Joel Borggrén-Franck
2010-12-12 19:39 ` Austin Clements
2010-12-12 22:01 ` servilio [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='AANLkTin2ocjB5u=hYBXoSUGw7PdV7HxKOHP4Yd2xHcL_@mail.gmail.com' \
--to=servilio@gmail.com \
--cc=amdragon@gmail.com \
--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).