From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] scary exception
Date: Mon, 27 Apr 2009 10:46:43 -0700 [thread overview]
Message-ID: <1240854270-sup-8870@entry> (raw)
In-Reply-To: <1240853542-sup-4778@tangerine.lanl.gov>
Reformatted excerpts from John Bent's message of 2009-04-27:
> I'm sorry. I don't remember. The timestamp on my sup executable says
> Jan 13 2009. I'll try to upgrade and see if I ever see this again.
Yeah, I think it was around March that things got merged in. Try it with
the latest & greatest and see if it happens again.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-27 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 3:28 John Bent
2009-04-27 17:25 ` William Morgan
2009-04-27 17:34 ` John Bent
2009-04-27 17:46 ` William Morgan [this message]
2009-05-24 5:54 ` John Bent
2009-05-27 16:03 ` William Morgan
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=1240854270-sup-8870@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