From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs24161fgb; Fri, 19 Mar 2010 12:43:38 -0700 (PDT) Received: by 10.229.189.16 with SMTP id dc16mr913944qcb.92.1269027818162; Fri, 19 Mar 2010 12:43:38 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 33si155559qyk.130.2010.03.19.12.43.37; Fri, 19 Mar 2010 12:43:38 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 7CD0718582EC; Fri, 19 Mar 2010 15:43:37 -0400 (EDT) Received: from mail-bw0-f212.google.com (mail-bw0-f212.google.com [209.85.218.212]) by rubyforge.org (Postfix) with ESMTP id 1C16718581FE for ; Fri, 19 Mar 2010 15:34:36 -0400 (EDT) Received: by bwz4 with SMTP id 4so3533161bwz.19 for ; Fri, 19 Mar 2010 12:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:cc:subject:from :to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=3pG/0TSw6BwyN9cv7leq1mktT0OTGa7ayLSeZiuoYu0=; b=nnEXbYPC1GlhSVKlgJaLPcCNo2RLa58xG5CBtnJ9ucudchV6OA6bWHapuGIblMh9QQ Uf5VjqiW608H+hCHkM7i1TlO0rSs7TyBllvx16K8eh00+nykIftlbjXiGa5jHABPF3+X SRoHkFwWOl2jYOe4JiHOc+RI9WDhHGR9dhMhs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=ANJaTOKbuf/omrw2BLkgsUovNP4Q93K08N6F0bQ2EzdzBLdyCLZ2T4+73pxdnXc4Cy AZAlR8q3eunSG3ktQVQf3X/c+/yQGG31zbC8ZfpDXSQTy4D5O0yJbHwxTC2UMd/I+GM2 ag2xLK1k044P4tnilrqK0d284x/30Evb7STus= Received: by 10.204.2.202 with SMTP id 10mr3324325bkk.206.1269027276009; Fri, 19 Mar 2010 12:34:36 -0700 (PDT) Received: from localhost (c-76-98-96-154.hsd1.nj.comcast.net [76.98.96.154]) by mx.google.com with ESMTPS id 14sm919203bwz.14.2010.03.19.12.34.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Mar 2010 12:34:35 -0700 (PDT) From: Eric Sherman To: Mark Alexander In-reply-to: <1269026068-sup-6868@r61> References: <1269012878-sup-691@midna.zekjur.net> <1269026068-sup-6868@r61> Date: Fri, 19 Mar 2010 15:34:32 -0400 Message-Id: <1269026805-sup-2720@changeling.local> 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 Fri Mar 19 15:17:01 -0400 2010: > Excerpts from Michael Stapelberg's message of Fri Mar 19 11:36:37 -0400 2010: > > the attached patch uses nanosecond resolution to generate the unique id for > > each message of a maildir. This is necessary because I have about 2000 messages > > which have the same mtime and size. > > This a great idea, but if I understand correctly, it requires a file > system that supports nanosecond resolution on timestamps, like ext4. > Those of us on ext3 are out of luck, apparently: > > https://ext4.wiki.kernel.org/index.php/Ext4_Howto#Inode-related_features Would inserting an SHA1 into the id solve these problems, or does it just introduce more problems? _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel