From: David Bremner <david@tethera.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] test: overhaul multipart test to test for improved message/rfc822 handling
Date: Mon, 05 Sep 2011 23:08:17 -0300 [thread overview]
Message-ID: <87wrdmv2we.fsf@zancas.localnet> (raw)
In-Reply-To: <1315249306-22328-1-git-send-email-jrollins@finestructure.net>
On Mon, 5 Sep 2011 12:01:46 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> The main goal of this overhaul is to define how message/rfc822 parts
> should be handled. message/rfc822 parts should be output in a similar
> fashion to the outer message, including some subset of the rfc822
> headers. The following decisions about formatting of message/rfc822
> parts were made:
I have pushed the remaining 3 patches in the series. Namely this one,
and the last 2 from the previous series. I added a brief note to the
commit message about the one test which fails. I think on the whole the
approach Jamie took of writing the test as the specification is the
correct one.
d
next prev parent reply other threads:[~2011-09-06 2:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 17:13 problems with message/rfc822 parts Jameson Graef Rollins
2011-06-06 0:29 ` improving message/rfc822 part handling Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 1/5] test: some small fixes to multipart test Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 2/5] test: Fix date in test message in " Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 3/5] test: overhaul multipart test to test for improved message/rfc822 handling Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 4/5] Improve handling of message/rfc822 parts by adding a new header_message_part function to the formating structure Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 5/5] emacs: Improve support for message/rfc822 parts Jameson Graef Rollins
2011-06-08 19:30 ` tweaks for handling parts in reply Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 1/4] test/multipart: test for absence of "Non-text part:" lines in reply for multipart/* and message/rfc822 parts Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 2/4] Fix notmuch-reply to not output "Non-text part:" lines for non-leafnode parts Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 3/4] test: test for absence of "Non-text part: application/pgp-*" lines in reply Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 4/4] Ignore "application/pgp-*" parts " Jameson Graef Rollins
2011-06-10 1:58 ` tweaks for handling " Austin Clements
2011-10-06 13:29 ` David Bremner
2011-10-06 17:24 ` Jameson Graef Rollins
2011-09-05 19:01 ` [PATCH] test: overhaul multipart test to test for improved message/rfc822 handling Jameson Graef Rollins
2011-09-06 2:08 ` David Bremner [this message]
2011-09-05 12:06 ` [PATCH 2/5] test: Fix date in test message in multipart test David Bremner
2011-06-06 0:33 ` improving message/rfc822 part handling Jameson Graef Rollins
2011-06-06 3:56 ` Jameson Graef Rollins
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=87wrdmv2we.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).