unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Cc: tomi.ollila@iki.fi
Subject: [PATCH v2 1/1] NEWS (for 0.15): Added note about Bcc & Reply-To headers in json output
Date: Fri, 16 Nov 2012 12:33:03 +0200	[thread overview]
Message-ID: <1353061983-7173-1-git-send-email-tomi.ollila@iki.fi> (raw)

notmuch show --format json now includes Bcc and Reply-To headers of
the message. Mention that in NEWS.
(Heavily modified version of text originally from Michal Nazarewicz.)
---

V2 of id:1352997830-1793-1-git-send-email-tomi.ollila@iki.fi
fixed the nitpick in id:20121115200001.GV22284@mit.edu ;)

Luckily preparing this patch was easy, I just edited the patch file,
then reapplied the patch with git am -- and before sending I will
reapply again to verify that I don't accidentally break things
while adding this comment.
Marking with notmuch::patch (only) as Michal acked the content already.

 NEWS | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/NEWS b/NEWS
index f134a22..4f4e2c3 100644
--- a/NEWS
+++ b/NEWS
@@ -12,6 +12,12 @@ Empty tag names and tags beginning with "-" are deprecated
   tags continues to be supported to allow cleanup of existing tags,
   but may be removed in a future release.
 
+Bcc and Reply-To headers are now available in notmuch show json output
+
+  The `notmuch show --format=json` now includes "Bcc" and "Reply-To" headers.
+  For example notmuch Emacs client can now have these headers visible
+  when the headers are added to the `notmuch-message-headers` variable.
+
 Library changes
 ---------------
 
-- 
1.8.0

             reply	other threads:[~2012-11-16 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 10:33 Tomi Ollila [this message]
2012-11-16 12:16 ` [PATCH v2 1/1] NEWS (for 0.15): Added note about Bcc & Reply-To headers in json output 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=1353061983-7173-1-git-send-email-tomi.ollila@iki.fi \
    --to=tomi.ollila@iki.fi \
    --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).