unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Peter Wang <novalazy@gmail.com>
To: notmuch@notmuchmail.org
Subject: [PATCH v2 0/3] indicate length of omitted body content
Date: Wed,  8 Aug 2012 22:27:49 +1000	[thread overview]
Message-ID: <1344428872-12374-1-git-send-email-novalazy@gmail.com> (raw)

The first commit is tangentally related.  An expected test case output
in test/crypto previously had a filename left unnormalised by
notmuch_json_show_sanitize because it was not followed by comma.
The next commit causes the comma to be present, breaking the expected
output.

In the 2nd commit, a content-transfer-encoding field was added and
comments clarified.

In the 3rd commit, the content-length of an encrypted attachment had
to be normalised because it varies between runs.

Peter Wang (3):
  test: normalize only message filenames in show json
  show: indicate length, encoding of omitted body content
  test: conform to content length, encoding fields

 devel/schemata   |    9 ++++++++-
 notmuch-show.c   |   14 ++++++++++++++
 test/crypto      |   30 +++++++++++++++++++++---------
 test/json        |    2 +-
 test/multipart   |   11 ++++++-----
 test/test-lib.sh |    2 +-
 6 files changed, 51 insertions(+), 17 deletions(-)

-- 
1.7.4.4

             reply	other threads:[~2012-08-08 12:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 12:27 Peter Wang [this message]
2012-08-08 12:27 ` [PATCH v2 1/3] test: normalize only message filenames in show json Peter Wang
2012-08-08 12:27 ` [PATCH v2 2/3] show: indicate length, encoding of omitted body content Peter Wang
2012-08-08 12:27 ` [PATCH v2 3/3] test: conform to content length, encoding fields Peter Wang
2012-10-20  2:21   ` Ethan Glasser-Camp
2012-10-21  3:03     ` Peter Wang
2012-10-21  3:04   ` [PATCH v3] " Peter Wang
2012-10-21 12:53     ` Ethan Glasser-Camp

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=1344428872-12374-1-git-send-email-novalazy@gmail.com \
    --to=novalazy@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).