From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Michael Stipicevic <stipredirect@gmail.com>
Cc: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Exception
Date: Fri, 01 Oct 2010 13:13:15 -0400 [thread overview]
Message-ID: <1285953175-sup-1593@ezyang> (raw)
In-Reply-To: <AANLkTi=DvF9DgNv2OxsB64b=GNjRm6TV12N=HRas89Dp@mail.gmail.com>
Excerpts from Michael Stipicevic's message of Fri Oct 01 00:52:18 -0400 2010:
> Did this happen right after you sent a message? I had to fix this by doing a
> dump and rebuilding the index.
Yep. Ouch! Although, I suppose there are worse things in life :-)
Cheers,
Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-10-01 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 19:19 Edward Z. Yang
2010-10-01 4:52 ` Michael Stipicevic
2010-10-01 17:13 ` Edward Z. Yang [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=1285953175-sup-1593@ezyang \
--to=ezyang@mit.edu \
--cc=stipredirect@gmail.com \
--cc=sup-devel@rubyforge.org \
/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