From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] [Crash] "thread_by_subject: true" leads to "wrong id called on nil"
Date: Tue, 11 Mar 2008 02:06:08 -0500 [thread overview]
Message-ID: <521619824.20080311020608@rice.edu> (raw)
In-Reply-To: <1205210652-sup-1364@amethyst>
Alexandra Walford @ 2008-3-10 11:45:43 PM
"[sup-talk] [Crash] "thread_by_subject: true" leads to "wrong id called on nil"" <mid:1205210652-sup-1364 at amethyst>
> I have managed to narrow down one particular crash to two messages
> sent to the sup-talk list. If I set up a new maildir containing only
> those two messages and a new sup config, accepting all sup-config
> defaults and changing thread_by_subject to true, then I can
> reproduce the crash reliably. The second message References: the
> first message, although the subjects are dissimilar.
Sorry! :-)
The first message was created with sup. The second with git's
send-email command. I've not looked at them closely, but the messages
may be malformed.
--
Christopher Warrington <chrisw at rice.edu>
"The next best thing to being clever is being able to quote someone
who is."
-Mary Poole
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 183 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080311/3ee207f6/attachment.bin
next prev parent reply other threads:[~2008-03-11 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 4:45 Alexandra Walford
2008-03-11 7:06 ` Christopher Warrington [this message]
2008-03-12 0:51 ` Michael Gurski
2008-03-14 18:51 ` William Morgan
2008-03-14 22:28 ` Alexandra Walford
2008-03-17 16:41 ` William Morgan
2008-03-18 12:35 ` Alexandra Walford
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=521619824.20080311020608@rice.edu \
--to=chrisw@rice.edu \
/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