From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs23603fgb; Fri, 19 Mar 2010 12:22:55 -0700 (PDT) Received: by 10.229.218.204 with SMTP id hr12mr4163855qcb.101.1269026575029; Fri, 19 Mar 2010 12:22:55 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 4si1315143qyk.95.2010.03.19.12.22.54; Fri, 19 Mar 2010 12:22:55 -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 7D1421598077; Fri, 19 Mar 2010 15:22:54 -0400 (EDT) Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by rubyforge.org (Postfix) with ESMTP id 3C5BD18581FE for ; Fri, 19 Mar 2010 15:22:49 -0400 (EDT) Received: by pwj1 with SMTP id 1so2613815pwj.23 for ; Fri, 19 Mar 2010 12:22:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:cc :subject:from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=fqnYSaCz96/bNFlzJAqohNg13uyrmpCPhYrD5PcASbY=; b=maWi0la+iIRfFoL4JrAJS6uCg1jsNwlDfTYXVNjs/S7W43uHYPrfVgR5l8Exgs+zr9 CX5vqOAj97i7juVgC/y3Vr7sGdR6OndLphhe+t+OsbOB1cGqf467oB8EN9XGp5Lg+f96 TscnZO8ajW+b4hGJr9WaTmQrOzoCmmbT7TQmw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=FhHcGvap5a0rIr32XkoDe23lprW9VtXTLy9SdZ8YkGplpbcOGM4O0I4KMao1mYJTZ6 JbrtnZquI5LI+p05JOPYibrThYS+d6NYGnGEc81QncImmORSVGghqhvDirvUwBYLdq9u 1xjaImXtb7Ur3Elyadb/qC7SHn9P0KqCRVhAQ= Received: by 10.115.64.27 with SMTP id r27mr1948958wak.6.1269026225714; Fri, 19 Mar 2010 12:17:05 -0700 (PDT) Received: from localhost (c-24-63-138-255.hsd1.vt.comcast.net [24.63.138.255]) by mx.google.com with ESMTPS id 23sm1019811pzk.6.2010.03.19.12.17.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Mar 2010 12:17:04 -0700 (PDT) From: Mark Alexander To: Michael Stapelberg In-reply-to: <1269012878-sup-691@midna.zekjur.net> References: <1269012878-sup-691@midna.zekjur.net> Date: Fri, 19 Mar 2010 15:17:01 -0400 Message-Id: <1269026068-sup-6868@r61> User-Agent: Sup/0.10.2 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 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 _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel