From: Tero Tilus <tero@tilus.net>
To: Eric Polino <aluink@gmail.com>, Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [sup-devel] Problems Syncing
Date: Fri, 22 Jan 2010 00:02:53 +0200 [thread overview]
Message-ID: <1264110830-sup-2631@tilus.net> (raw)
In-Reply-To: <1263931111-sup-1739@europa>
Eric Polino, 2010-01-19 22:04:
> I did find a place that was saying that getting the lastest version
> of sup from the git repository could fix this problem...it didn't.
Try pulling all the mails down using offlineimap or similar and then
index the local mailstore. Also, use Xapian index, not Ferret.
ps. Imo this kind of things belong to sup-talk, not sup-devel.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
parent reply other threads:[~2010-01-21 22:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1263931111-sup-1739@europa>]
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=1264110830-sup-2631@tilus.net \
--to=tero@tilus.net \
--cc=aluink@gmail.com \
--cc=sup-talk@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