From: tpo2@sourcepole.ch (Tomas Pospisek ML)
Subject: [sup-talk] bug: reproducable Sup crash, ferret-less rewrite?
Date: Sat, 01 Nov 2008 22:13:44 +0000 [thread overview]
Message-ID: <J4OdBBA7.1225577624.9061510.tpo2@192.168.3.7> (raw)
In-Reply-To: <C5313447.2C02%chrisw@rice.edu>
On 11/1/2008, "Christopher Warrington" <chrisw at rice.edu> wrote:
>"Tomas Pospisek ML" <tpo2 at sourcepole.ch> @ 2008-10-31 6:52 PM:
>
>> I can not find any trace of the latter, i.e. Sup's source code
>> repository at Gitorious [3] doesn't show any ferret amputation. Are
>> you, William Morgan working on a Sup version that doesn't show that
>> supposedly ferret induced crashiness? Possibly your "private" branch
>> is not ready yet and not accessible?
>
>See these blog posts about "Sup: The Server!"
>http://all-thing.net/search/label/sup
Very interesting, thanks. So, while William Morgan is pursuing his
ambitous project [1]:
- has anybody tried to swap Ferret with any other indexer [also in [1]]?
- has anybody tried to fix the index corruption / ferret crash bug [2]?
*t
[1] http://rubyforge.org/pipermail/sup-talk/2008-July/001593.html
[2] http://ferret.davebalmain.com/trac/ticket/279
next prev parent reply other threads:[~2008-11-01 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 23:52 Tomas Pospisek ML
2008-11-01 3:16 ` Christopher Warrington
2008-11-01 22:13 ` Tomas Pospisek ML [this message]
2008-11-02 18:30 ` 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=J4OdBBA7.1225577624.9061510.tpo2@192.168.3.7 \
--to=tpo2@sourcepole.ch \
/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