From: David Bremner <david@tethera.net>
To: Aaron Ecay <aaronecay@gmail.com>, Jani Nikula <jani@nikula.org>,
notmuch@notmuchmail.org
Subject: Re: [RFC] [PATCH] lib/database.cc: change how the parent of a message is calculated
Date: Sun, 03 Mar 2013 22:45:55 -0400 [thread overview]
Message-ID: <87ppzfzxuk.fsf@zancas.localnet> (raw)
In-Reply-To: <87sj4cvy0h.fsf@gmail.com>
Aaron Ecay <aaronecay@gmail.com> writes:
> git send-email is mad about lines >998 characters in the test patch, so
> I’m sending the patches as attachments to this email. (Is there a
> better way to include the expected output of a notmuch command which
> outputs long lines in a test script?)
What about pretty printing the json in the source?
test_expect_equal_json canonicalizes both arguments before comparing, so
it should be ok.
d
next prev parent reply other threads:[~2013-03-04 2:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 23:50 [RFC] [PATCH] lib/database.cc: change how the parent of a message is calculated Aaron Ecay
2013-02-26 9:19 ` Jani Nikula
2013-02-26 19:40 ` Aaron Ecay
2013-02-28 19:41 ` Jani Nikula
2013-03-01 17:06 ` Jani Nikula
2013-03-03 23:46 ` Aaron Ecay
2013-03-03 23:55 ` Aaron Ecay
2013-03-04 2:45 ` David Bremner [this message]
2013-03-06 3:31 ` [PATCH 1/2] test: add tests for the handling of References and In-Reply-To headers Aaron Ecay
2013-03-06 3:31 ` [PATCH 2/2] lib/database.cc: change how the parent of a message is calculated Aaron Ecay
2013-05-04 14:10 ` David Bremner
2013-05-04 16:24 ` Jani Nikula
2013-05-14 0:43 ` David Bremner
2013-05-04 14:01 ` [PATCH 1/2] test: add tests for the handling of References and In-Reply-To headers David Bremner
2013-05-04 14:03 ` David Bremner
2013-05-04 16:23 ` Jani Nikula
2013-03-04 5:59 ` [RFC] [PATCH] lib/database.cc: change how the parent of a message is calculated Tomi Ollila
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=87ppzfzxuk.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=aaronecay@gmail.com \
--cc=jani@nikula.org \
--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).