From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.87.14 with SMTP id k14cs1121579agb; Mon, 28 Dec 2009 13:06:45 -0800 (PST) Received: by 10.224.87.81 with SMTP id v17mr7755687qal.108.1262034405437; Mon, 28 Dec 2009 13:06:45 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 3si18113499qyk.0.2009.12.28.13.06.45; Mon, 28 Dec 2009 13:06:45 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2284418582FF; Mon, 28 Dec 2009 16:06:45 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 0066918582C7 for ; Mon, 28 Dec 2009 16:06:39 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NPMnX-0006ig-IW for sup-talk@rubyforge.org; Mon, 28 Dec 2009 13:06:39 -0800 From: William Morgan To: sup-talk In-reply-to: <1262031833-sup-9424@sgoldmanlinux.tower-research.com> References: <4B384745.7080207@exys.org> <1262013098-sup-6005@masanjin.net> <4B386D1D.4000609@exys.org> <1262027723-sup-4292@tilus.net> <1262031447-sup-787@masanjin.net> <1262031833-sup-9424@sgoldmanlinux.tower-research.com> Date: Mon, 28 Dec 2009 13:06:39 -0800 Message-Id: <1262034335-sup-9328@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] sup with 120K mail X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Steve Goldman's message of 2009-12-28: > Is Xapian sup fully functional? Last I read, there were some critical > functions that were supported. Functional enough that it's going to be the default in the next release of Sup, and you're going to get yelled at for Ferret. A few things don't work or are weird, but it could break everything and still provide a better user experience than Ferret. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk