From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] (Double/guarded) keypress to show all threads
Date: Mon, 14 Jan 2008 10:54:26 +0000 [thread overview]
Message-ID: <1200307947-sup-1357@tomsk> (raw)
In-Reply-To: <1200272179-sup-6412@south>
On 14.1.2008, William Morgan wrote:
> The general slowness of this type of operation in Sup is a real
> problem, IMO. I think we can go a long way by caching threading
> information, though of course that's at the expense of disk space.
Disk space is cheap :) So if this gets us a speed up I think its worth
it. If people are worried about that sort of thing it could be a
configurable option.
Marcus
next prev parent reply other threads:[~2008-01-14 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 17:20 Marcus Williams
2008-01-13 5:30 ` William Morgan
2008-01-13 15:57 ` Nicolas Pouillard
2008-01-13 18:16 ` Marcus Williams
2008-01-14 1:06 ` William Morgan
2008-01-14 10:54 ` Marcus Williams [this message]
2008-01-15 4:49 ` William Morgan
2008-01-15 12:29 ` [sup-talk] [PATCH] Search all threads with option to cancel Marcus Williams
2008-01-16 4:30 ` William Morgan
2008-01-16 10:47 ` Marcus Williams
2008-01-16 21:09 ` 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=1200307947-sup-1357@tomsk \
--to=marcus-sup@bar-coded.net \
/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