From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs27026fgb; Fri, 19 Mar 2010 14:22:29 -0700 (PDT) Received: by 10.224.40.9 with SMTP id i9mr1408227qae.29.1269033748640; Fri, 19 Mar 2010 14:22:28 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 41si2980698qyk.87.2010.03.19.14.22.28; Fri, 19 Mar 2010 14:22:28 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 1C6DE1779938; Fri, 19 Mar 2010 17:22:28 -0400 (EDT) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id 83C9F18582D5 for ; Fri, 19 Mar 2010 17:18:01 -0400 (EDT) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1NsjZm-0001h8-9p; Fri, 19 Mar 2010 17:17:50 -0400 From: Rich Lane To: Mark Alexander In-reply-to: <1269030873-sup-4844@r61> References: <1269012878-sup-691@midna.zekjur.net> <1269026068-sup-6868@r61> <1269026769-sup-3830@midna.zekjur.net> <1269027265-sup-5150@pinkfloyd.chass.utoronto.ca> <1269027991-sup-5670@midna.zekjur.net> <1269030873-sup-4844@r61> Date: Fri, 19 Mar 2010 17:17:50 -0400 Message-Id: <1269032592-sup-2403@zyrg.net> User-Agent: Sup/git Cc: sup-devel Subject: Re: [sup-devel] [PATCH 2/2] Use nanosecond resolution of mtime for generating the unique id for each message X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion 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-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Mark Alexander's message of 2010-03-19 16:35:38 -0400: > Excerpts from Michael Stapelberg's message of Fri Mar 19 15:47:53 -0400 2010: > > Excerpts from Ben Walton's message of 2010-03-19 20:35:31 +0100: > > > Isn't there a more portable solution? > > There is: Rich mentioned that proper move/delete handling for maildirs also > > solves the problem. > > I must have missed that message. What is the proposed solution? > How does it solve the problem of out-of-order maildir IDs? Notmuch implements this correctly. They essentially keep a sorted list of mail filenames in the index and then iterate over that and the sorted list of the filenames that are currently in the maildir to detect inserts, deletes, and renames. I just rebased and pushed a multiple-locations branch I've had sitting around to mainline. It's probably buggy. It's been a while since I thought about this problem, but I think keeping track of multiple locations (source/source info) for a single message (identified by message-id) should make the maildir logic simpler. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel