From: aardvark@saintaardvarkthecarpeted.com (Saint Aardvark the Carpeted)
Subject: [sup-talk] Exception in sup-git when sending postponed email
Date: Fri, 12 Dec 2008 06:01:14 -0800 [thread overview]
Message-ID: <20081212140114.GI25721@danconia.atlantis.saintaardvarkthecarpeted.com> (raw)
In-Reply-To: <1229046535-sup-9338@entry>
William Morgan disturbed my sleep to write:
> Thanks for the very details report, but I'm having a hard time imagining
> what could've caused this. It almost seems like a memory corruption
> issue. Has it (or anything like it) happened again?
Not yet. I'll keep an eye out and will try stress-testing the memory
on this box.
Thanks,
Hugh
--
Saint Aardvark the Carpeted
http://saintaardvarkthecarpeted.com
Because the plural of Anecdote is Myth.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20081212/cf731888/attachment.bin>
prev parent reply other threads:[~2008-12-12 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 21:11 Saint Aardvark the Carpeted
2008-12-12 1:50 ` William Morgan
2008-12-12 14:01 ` Saint Aardvark the Carpeted [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=20081212140114.GI25721@danconia.atlantis.saintaardvarkthecarpeted.com \
--to=aardvark@saintaardvarkthecarpeted.com \
/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