From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Tomi Ollila <tomi.ollila@iki.fi>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH 1/5] test: two new messages for the 'broken' corpus
Date: Sun, 15 Apr 2018 00:36:02 -0700 [thread overview]
Message-ID: <87fu3wsyzh.fsf@fifthhorseman.net> (raw)
In-Reply-To: <m27ep9s9z0.fsf@guru.guru-group.fi>
On Sun 2018-04-15 01:24:03 +0300, Tomi Ollila wrote:
> Instead the huge amount of noise in these messages, I suggest:
I agree with Tomi's suggestion that the simplest possible messages are
the best for testing (i haven't tried either of them yet myself though).
--dkg
next prev parent reply other threads:[~2018-04-15 15:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 1:46 reference loop fix and tests, v2 David Bremner
2018-04-14 1:46 ` [PATCH 1/5] test: two new messages for the 'broken' corpus David Bremner
2018-04-14 22:24 ` Tomi Ollila
2018-04-15 7:36 ` Daniel Kahn Gillmor [this message]
2018-04-14 1:46 ` [PATCH 2/5] test: add known broken test for indexing an In-Reply-To loop David Bremner
2018-04-14 1:46 ` [PATCH 3/5] lib: break reference loop by choosing arbitrary top level msg David Bremner
2018-04-15 7:38 ` Daniel Kahn Gillmor
2018-04-14 1:46 ` [PATCH 4/5] test: add second reference loop test David Bremner
2018-04-14 1:46 ` [PATCH 5/5] NEWS: add item for reference loop fix David Bremner
2018-04-20 18:31 ` v3 " David Bremner
2018-04-20 18:31 ` [PATCH 1/6] test: two new messages for the 'broken' corpus David Bremner
2018-04-20 18:31 ` [PATCH 2/6] test: add known broken test for indexing an In-Reply-To loop David Bremner
2018-04-20 18:31 ` [PATCH 3/6] lib: break reference loop by choosing arbitrary top level msg David Bremner
2018-04-20 18:31 ` [PATCH 4/6] NEWS: add item for reference loop fix David Bremner
2018-04-20 18:31 ` [PATCH 5/6] test: add known broken test for thread ordering from a loop David Bremner
2018-04-20 18:31 ` [PATCH 6/6] lib: choose oldest message when breaking reference loops David Bremner
2018-04-21 17:53 ` Tomi Ollila
2018-04-25 1:52 ` David Bremner
2018-04-25 11:48 ` Tomi Ollila
2018-04-25 20:41 ` reference loop fix and tests, v2 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=87fu3wsyzh.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).