Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] header cache
Date: Tue, 15 Jan 2008 19:24:47 -0800	[thread overview]
Message-ID: <1200453820-sup-4777@south> (raw)
In-Reply-To: <704d6aa20801150454j635ed24p63fd544579c6e148@mail.gmail.com>

Reformatted excerpts from Giorgio Lando's message of 2008-01-15:
> My "All mail" includes approximately 40000 messages so the fetching of
> IMAP headers is highly time-consuming (also the initial sup-sync took
> about 8 hours, but this happens only one time).
> 
> I see that in TODO the header cache is scheduled for the 0.4 release.
> So am I correct to expect it quite soon?

Yes, I have a stub implementation in the works that should be ready for
testing soon. I'll focus more attention on it now that I have a
customer. :)

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2008-01-16  3:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 12:54 Giorgio Lando
2008-01-16  3:24 ` William Morgan [this message]
2008-01-16 20:26   ` Giorgio Lando
2008-01-16 20:48     ` William Morgan
2008-01-16 22:04       ` Giorgio Lando
2008-01-16 22:58         ` Alec Berryman
2008-01-16 23:36           ` Giorgio Lando
2008-01-17  8:13         ` Nicolas Pouillard
2008-01-17 11:40           ` Giorgio Lando
2008-01-17 14:56             ` Nicolas Pouillard
2008-01-22  2:36               ` William Morgan
2008-01-22  8:40                 ` Nicolas Pouillard
2008-01-23 20:33                   ` Gabriel Sean Farrell
     [not found]                   ` <1201071069-sup-6394@south>
     [not found]                     ` <1201079068-sup-438@ausone.inria.fr>
2008-01-25  3:28                       ` William Morgan
2008-01-25  8:50                         ` Nicolas Pouillard

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=1200453820-sup-4777@south \
    --to=wmorgan-sup@masanjin.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