[PATCH 4/4] Update NEWS for user.other_name
[notmuch-archives.git] / 54 / a658c7b9e1699e7961a1c189941d51ca070ec8
1 Return-Path: <dkg@fifthhorseman.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 arlo.cworth.org (Postfix) with ESMTP id 026486DE01C2\r
6  for <notmuch@notmuchmail.org>; Tue,  9 Aug 2016 11:50:15 -0700 (PDT)\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -0.052\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-0.052 tagged_above=-999 required=5\r
12  tests=[AWL=-0.052] autolearn=disabled\r
13 Received: from arlo.cworth.org ([127.0.0.1])\r
14  by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
15  with ESMTP id XpzgwxTuQ3wT for <notmuch@notmuchmail.org>;\r
16  Tue,  9 Aug 2016 11:50:05 -0700 (PDT)\r
17 Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118])\r
18  by arlo.cworth.org (Postfix) with ESMTP id 91E016DE015B\r
19  for <notmuch@notmuchmail.org>; Tue,  9 Aug 2016 11:50:05 -0700 (PDT)\r
20 Received: from fifthhorseman.net (unknown [38.109.115.130])\r
21  by che.mayfirst.org (Postfix) with ESMTPSA id D8640F993;\r
22  Tue,  9 Aug 2016 14:50:03 -0400 (EDT)\r
23 Received: by fifthhorseman.net (Postfix, from userid 1000)\r
24  id 87340200E2; Tue,  9 Aug 2016 14:34:58 -0400 (EDT)\r
25 From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
26 To: Matthias Beyer <mail@beyermatthias.de>, notmuch@notmuchmail.org\r
27 Subject: Re: How does notmuch track mails?\r
28 In-Reply-To: <20160809140223.GH3832@yuu>\r
29 References: <20160809140223.GH3832@yuu>\r
30 User-Agent: Notmuch/0.22.1+88~g8d09e96 (https://notmuchmail.org) Emacs/24.5.1\r
31  (x86_64-pc-linux-gnu)\r
32 Date: Tue, 09 Aug 2016 14:34:50 -0400\r
33 Message-ID: <87twetvlit.fsf@alice.fifthhorseman.net>\r
34 MIME-Version: 1.0\r
35 Content-Type: multipart/signed; boundary="=-=-=";\r
36  micalg=pgp-sha512; protocol="application/pgp-signature"\r
37 X-BeenThere: notmuch@notmuchmail.org\r
38 X-Mailman-Version: 2.1.20\r
39 Precedence: list\r
40 List-Id: "Use and development of the notmuch mail system."\r
41  <notmuch.notmuchmail.org>\r
42 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
43  <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
44 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
45 List-Post: <mailto:notmuch@notmuchmail.org>\r
46 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
47 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
48  <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
49 X-List-Received-Date: Tue, 09 Aug 2016 18:50:15 -0000\r
50 \r
51 --=-=-=\r
52 Content-Type: text/plain\r
53 Content-Transfer-Encoding: quoted-printable\r
54 \r
55 On Tue 2016-08-09 10:02:23 -0400, Matthias Beyer wrote:\r
56 \r
57 > I wonder how notmuch tracks mails. Lets assume that we have a big\r
58 > Maildir tree - mails move around all the time - how does notmuch\r
59 > (re)find them? Is there a unique way to identify an email? As far as I\r
60 > know isn't the message id one of them, right?\r
61 \r
62 notmuch uses message-id to identify individual mails.   this is a nice\r
63 simplification, but it leaves open some potentially problematic\r
64 situations that we have still never resolved (e.g. matching message-ids\r
65 on distinct mail, whether via malice or incompetence).\r
66 \r
67 notmuch has maildir scanning code that is clever about tracking which\r
68 parts of various subtrees have changed recently and avoids having to\r
69 re-scan them if they haven't changed (this does require some cooperation\r
70 From=20the filesystem -- if you have an absolutely terrible filesystem, i\r
71 don't know how notmuch would handle the situation).\r
72 \r
73         --dkg\r
74 \r
75 \r
76 --=-=-=\r
77 Content-Type: application/pgp-signature; name="signature.asc"\r
78 \r
79 -----BEGIN PGP SIGNATURE-----\r
80 \r
81 iQJ8BAEBCgBmBQJXqiJKXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
82 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFREIyRTc0RjU2RkNGMkI2NzI5N0I3MzUy\r
83 NEVDRkY1QUZGNjgzNzBBAAoJECTs/1r/aDcKuH4P/Aoayij5LHKnLfFm17MBtK2i\r
84 +dLJVhwM0n+58LY/frKYD3KRyR0oXhE1f1zo1FA76mS9vHb35t37IahLuYhOwuNZ\r
85 YaXHgMwcvwlAseeYDz1gmCRxyJ1LrcFPGrjXWhWoPpFnbKkQc1rPjocOwudNQiiA\r
86 PcXHEowjFduX1OFc6q24AxS5RdfcvwHL4/gMoi4Ufvvir2PGAAoETdsU+vhgBfc6\r
87 1fAQwHLXLIqX0MrGzQCqdA0PuLCUp/IlehkbGbZIVxPZuo72GiuNcBFfLO5VR6mr\r
88 amdYsN+PvgvUUm7q5YpZKyeXZZbhELALc4Bw6Pc0qbpJLmMqjWKTKQI5Uifggm9a\r
89 J1jqloDwzTzgWo/JC+wm4BkjeIVq1he0Sbk43NqFbdHWDle333cMM3Xq3xyXrYOE\r
90 ae2AyYoxlnuQnSJoG5kVKiulfOAcGPCS4CUJ2UyDn0YuJV+VuzdP5dJlm3SlZDRv\r
91 dVmrGhPCsA+GAy6ptL/KC9TUwSn9XmXe+WiBPFlU1QpLSj+y1Otw1z8nWy1aAPs2\r
92 +pgps8Pa6Wc57RYyuo+X3NQ9OTZpCxMkRafOb/uFKLAgpOTt9NB+/8FmyMkhnlH4\r
93 5kCd+SSACLQY2QY5Y04/owr12JNrFVXxkL+sRxR34APLud5QYuV9nIiQ/Orsw05r\r
94 a7hXYnhtZab3PX1mSxRS\r
95 =zHYD\r
96 -----END PGP SIGNATURE-----\r
97 --=-=-=--\r