From: Moritz Wilhelmy <moritz+sup@wzff.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Sat, 23 Oct 2010 01:32:46 +0200 [thread overview]
Message-ID: <1287790246-sup-3757@niflheimr> (raw)
In-Reply-To: <1287770413-sup-279@blake>
Excerpts from Shadowfirebird's message of Fri Oct 22 20:02:39 +0200 2010:
> Oh gods. I'm emacs-phobic.
I meant to say, you could try if notmuch performs any better. You don't have to
use the emacs extension, it also works as plain command line command.
If the performance is not better, it's probably your NFS.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-10-23 0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 9:23 Shadowfirebird
2010-10-22 10:40 ` Amadeusz Żołnowski
2010-10-22 11:48 ` Shadowfirebird
2010-10-22 13:09 ` Moritz Wilhelmy
2010-10-22 18:02 ` Shadowfirebird
2010-10-22 23:32 ` Moritz Wilhelmy [this message]
2010-10-22 11:04 ` Gaute Hope
2010-10-22 11:16 ` Philipp Überbacher
2010-10-22 12:21 ` Ben Walton
2010-10-22 12:38 ` Mark Alexander
2010-10-22 13:03 ` Shadowfirebird
2010-10-22 16:28 ` Mark Alexander
2010-10-22 17:19 ` Sascha Silbe
2010-10-22 19:56 ` Shadowfirebird
2010-10-23 8:28 ` Sascha Silbe
2010-10-23 10:42 ` Shadowfirebird
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=1287790246-sup-3757@niflheimr \
--to=moritz+sup@wzff.de \
--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