1 Return-Path: <michiel@michielbuddingh.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 1D077431FBC
\r
6 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 07:57:55 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id uOybpHLdYlCE for <notmuch@notmuchmail.org>;
\r
11 Sun, 22 Nov 2009 07:57:53 -0800 (PST)
\r
12 Received: from aegir.org.uk (aegir.org.uk [87.238.170.13])
\r
13 by olra.theworths.org (Postfix) with ESMTP id 7B73A431FC0
\r
14 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 07:57:53 -0800 (PST)
\r
15 Received: from localhost.localdomain (109-9-ftth.onsnetstudenten.nl
\r
17 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
18 (No client certificate requested)
\r
19 by aegir.org.uk (Postfix) with ESMTPSA id 904662E01B;
\r
20 Sun, 22 Nov 2009 16:57:52 +0100 (CET)
\r
21 Date: Sun, 22 Nov 2009 16:57:52 +0100
\r
22 From: Michiel Buddingh' <michiel@michielbuddingh.net>
\r
23 To: notmuch@notmuchmail.org, cworth@cworth.org
\r
24 Message-ID: <4b095f80.oVC2da9Z18jqqm5n%michiel@michielbuddingh.net>
\r
25 References: <87fx8bygi7.fsf@linux.vnet.ibm.com>
\r
26 <87bpiv4t9h.fsf@yoom.home.cworth.org>
\r
27 <87y6lz39nd.fsf@yoom.home.cworth.org>
\r
28 <20091121221207.GB17268@jukie.net>
\r
29 <9cce5525b093b87fe74d427954ffad89@localhost>
\r
30 <87d43b2oif.fsf@yoom.home.cworth.org>
\r
31 <9bfdedddeab9c58cd45d8d448323d0fc@localhost>
\r
32 <87fx86g39u.fsf@yoom.home.cworth.org>
\r
33 In-Reply-To: <87fx86g39u.fsf@yoom.home.cworth.org>
\r
34 User-Agent: Heirloom mailx 12.4 7/29/08
\r
36 Content-Type: text/plain; charset=us-ascii
\r
37 Content-Transfer-Encoding: 7bit
\r
38 Subject: Re: [notmuch] [PATCH] notmuch: Add Maildir directory name as tag
\r
40 X-BeenThere: notmuch@notmuchmail.org
\r
41 X-Mailman-Version: 2.1.12
\r
43 List-Id: "Use and development of the notmuch mail system."
\r
44 <notmuch.notmuchmail.org>
\r
45 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
47 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
48 List-Post: <mailto:notmuch@notmuchmail.org>
\r
49 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
50 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
52 X-List-Received-Date: Sun, 22 Nov 2009 15:57:55 -0000
\r
54 Carl Worth <cworth@cworth.org> wrote:
\r
56 > > A Maildir-aware notmuch could incorporate this to be far more
\r
57 > > resistant to bulk mail moves done by other clients, by using
\r
58 > > filename lookups to avoid accessing and parsing the mail
\r
59 > > files themselves.
\r
61 > I don't think opening a file to read out a message ID will ever be
\r
62 > a bottleneck. But yes, we could take advantage of the unique name
\r
63 > if we insisted that the storage have it.
\r
65 I'm not so sure. On traditional unix-like filesystems, every file
\r
66 access is another potential disk seek.
\r
68 People use a lot of different strategies for keeping their mail
\r
69 accessible and performant; you yourself, I gather, use non-semantic
\r
70 directories mainly intended to keep the number of files per directory
\r
71 low; others store their mail per month, or per year.
\r
73 I might choose to move all my mail from 2008 from my INBOX to the
\r
74 folder Archive.2008; such moves may change the paths of thousands
\r
75 of messages at a time.
\r
77 > Personally, I still regularly end up indexing stuff that's not
\r
78 > in proper maildir format, (like just manually copying a mail
\r
79 > file "foo" down into a directory that I know isn't being delivered
\r
80 > to by any MDA but that I want notmuch to index.) Maybe that's just
\r
81 > me, because I'm always bringing up little things for debugging,
\r
82 > etc. But it is convenient at least.
\r
84 Oh true. And it occurs to me that notmuch is a quite sensible
\r
85 companion tool to MH users (if they're still around in any numbers)
\r
87 > Actually, I don't think that's true at all. Notmuch is definitely
\r
88 > intended to become a lot more than it is right now. And if it's not
\r
89 > making it easy for you to deal with mail the way you'd like to, then
\r
90 > we definitely do want to look into expanding notmuch to be able to
\r
93 Thanks for your consideration; on the other hand, I do think that it
\r
94 is a good idea not to make matters more complex than they need to be,
\r
95 so I can certainly sympathise with the principles you've set for this
\r