Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] updated xapian experimental branch
Date: Tue, 03 Nov 2009 11:12:11 -0500	[thread overview]
Message-ID: <1257263951-sup-6837@zyrg.net> (raw)
In-Reply-To: <1257237468-sup-5663@peray>

Excerpts from Nicolas Pouillard's message of Tue Nov 03 03:39:48 -0500 2009:
> What are non simple queries which would cause 'red X's to appear? My guess
> is that since we cannot change other attributes than the labels, we can
> statically know if the thread is still relevant without the label. No?

is:inbox OR foo

We have to use xapian to check relevance here because of the fulltext
term 'foo'.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-11-03 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 23:42 Rich Lane
2009-11-02 12:08 ` William Morgan
2009-11-03  3:48   ` Rich Lane
2009-11-03  8:39     ` Nicolas Pouillard
2009-11-03 16:12       ` Rich Lane [this message]
2009-11-03 16:15         ` 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=1257263951-sup-6837@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=nicolas.pouillard@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