From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Unit tests, part 2
Date: Thu, 03 Jan 2008 21:04:53 -0800 [thread overview]
Message-ID: <1199422670-sup-6990@south> (raw)
In-Reply-To: <1197741811-sup-1386@arlanda>
Hi Ismo,
Sorry for the delay on this. I've added the tests to git. Thank you very
much!
Excerpts from Ismo Puustinen's message of Sat Dec 15 10:25:35 -0800 2007:
> The difference to previous tests is that this test actually currently
> fails: for some reason, dividing a message body into chunks doesn't
> succeed. The message in question is an actual email message sent to
> vim-mac mailing list; only the names and email addresses have been
> obscured. I selected the message for the tests because it kept
> crashing my sup-sync. :-)
Definitely an RMail bug. I've committed a workaround to git so that Sup
doesn't crash, at least...
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-01-04 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 18:25 Ismo Puustinen
2008-01-04 5:04 ` William Morgan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1199422670-sup-6990@south \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox