unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: micah anderson <micah@riseup.net>
To: Olly Betts <olly@survex.com>,
	Jameson Rollins <jrollins@finestructure.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Backport of Xapian term update optimisation
Date: Thu, 04 Feb 2010 11:55:44 -0500	[thread overview]
Message-ID: <87aavp6iun.fsf@lillypad.riseup.net> (raw)
In-Reply-To: <20100204024524.GF22545@survex.com>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

On Thu, 4 Feb 2010 02:45:24 +0000, Olly Betts <olly@survex.com> wrote:
> On Wed, Feb 03, 2010 at 02:35:14PM -0500, Jameson Rollins wrote:
> > On Thu, 28 Jan 2010 00:06:59 +0000 (UTC), Olly Betts <olly@survex.com> wrote:
> >
> > I just installed this new version from a Debian experimental repo,
> > rebuilt notmuch against the new installation, and everything seems to be
> > working great.  I'll report back any issues to the BTS.  Thanks again.
> 
> Thanks.  Are you seeing the expected speed improvement?

Once this is available in unstable, the notmuch package should be
re-uploaded with a build-dependency on this version so that the package
users see the speed improvement. As it is now, the debian package is
pretty slow.

What is the expected time-frame for moving this out of an experimental
stage into unstable? Presumably this is a more proper release by Xapian?

micah

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2010-02-04 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  0:06 Backport of Xapian term update optimisation Olly Betts
2010-02-03 19:35 ` Jameson Rollins
2010-02-04  2:45   ` Olly Betts
2010-02-04  3:21     ` Jameson Rollins
2010-02-04 16:55     ` micah anderson [this message]
2010-02-04 23:23       ` Olly Betts
2010-02-12  8:08         ` David Edmondson
2010-02-15  1:16           ` Olly Betts

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87aavp6iun.fsf@lillypad.riseup.net \
    --to=micah@riseup.net \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    --cc=olly@survex.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).