From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup-mail crash
Date: Thu, 12 Feb 2009 13:58:20 -0800 [thread overview]
Message-ID: <1234475856-sup-8907@entry> (raw)
In-Reply-To: <1234268739-sup-5896@tomsk>
Reformatted excerpts from Marcus Williams's message of 2009-02-10:
> I can probably update and get stack trace if its any use.
Yeah, I'd be interested in this. There are definite mbox problems but I
don't think they are new ones, and they don't involve anything with
hashes AFAIK.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-02-12 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 22:26 Simon Raven
2009-02-09 22:41 ` Tomas Pospisek Mailing Lists
2009-02-09 23:09 ` William Morgan
2009-02-10 12:28 ` Marcus Williams
2009-02-12 21:58 ` William Morgan [this message]
2009-02-12 22:21 ` [sup-talk] [PATCH] " Rick Tessner
2009-03-22 17:46 ` William Morgan
2009-03-23 0:04 ` Decklin Foster
2009-02-11 23:05 ` [sup-talk] " Tomas Pospisek Mailing Lists
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=1234475856-sup-8907@entry \
--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