Re: [PATCH v4 10/16] Add n_d_add_message_with_indexopts (extension of n_d_add_message)
[notmuch-archives.git] / c2 / 7f7bcfdc534499fb9589f4893fe5bc8ed9d17a
1 Return-Path: <jrollins@finestructure.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 0EF21431FBD\r
6         for <notmuch@notmuchmail.org>; Sun, 23 Mar 2014 16:54:55 -0700 (PDT)\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -2.3\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
12         tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\r
13 Received: from olra.theworths.org ([127.0.0.1])\r
14         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
15         with ESMTP id iA7mxs8RTtK9 for <notmuch@notmuchmail.org>;\r
16         Sun, 23 Mar 2014 16:54:51 -0700 (PDT)\r
17 Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
18         [131.215.239.19])\r
19         by olra.theworths.org (Postfix) with ESMTP id 0DF84431FB6\r
20         for <notmuch@notmuchmail.org>; Sun, 23 Mar 2014 16:54:51 -0700 (PDT)\r
21 Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
22         by fire-doxen-postvirus (Postfix) with ESMTP id 9C5162E50E08;\r
23         Sun, 23 Mar 2014 16:54:50 -0700 (PDT)\r
24 X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
25 Received: from finestructure.net (unknown [198.129.209.100])\r
26         (Authenticated sender: jrollins)\r
27         by fire-doxen-submit (Postfix) with ESMTP id DFEE22E50B36;\r
28         Sun, 23 Mar 2014 16:54:49 -0700 (PDT)\r
29 Received: by finestructure.net (Postfix, from userid 1000)\r
30         id 6B5CE600D3; Sun, 23 Mar 2014 16:54:49 -0700 (PDT)\r
31 From: Jameson Graef Rollins <jrollins@finestructure.net>\r
32 To: Jani Nikula <jani@nikula.org>, David Bremner <david@tethera.net>,\r
33         notmuch@notmuchmail.org\r
34 Subject: Re: [PATCH 2/2] notmuch-new: block database upgrades in default\r
35         configuration.\r
36 In-Reply-To: <87ppldrocd.fsf@nikula.org>\r
37 References: <87bnx4jyyp.fsf@servo.finestructure.net>\r
38         <1395541573-2417-1-git-send-email-david@tethera.net>\r
39         <1395541573-2417-3-git-send-email-david@tethera.net>\r
40         <87ppldrocd.fsf@nikula.org>\r
41 User-Agent: Notmuch/0.17+134~g31849a1 (http://notmuchmail.org) Emacs/24.3.1\r
42         (x86_64-pc-linux-gnu)\r
43 Date: Sun, 23 Mar 2014 16:54:47 -0700\r
44 Message-ID: <8738i8eaig.fsf@servo.finestructure.net>\r
45 MIME-Version: 1.0\r
46 Content-Type: multipart/signed; boundary="=-=-=";\r
47         micalg=pgp-sha256; protocol="application/pgp-signature"\r
48 X-BeenThere: notmuch@notmuchmail.org\r
49 X-Mailman-Version: 2.1.13\r
50 Precedence: list\r
51 List-Id: "Use and development of the notmuch mail system."\r
52         <notmuch.notmuchmail.org>\r
53 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
54         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
55 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
56 List-Post: <mailto:notmuch@notmuchmail.org>\r
57 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
58 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
59         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
60 X-List-Received-Date: Sun, 23 Mar 2014 23:54:55 -0000\r
61 \r
62 --=-=-=\r
63 Content-Type: text/plain\r
64 \r
65 On Sun, Mar 23 2014, Jani Nikula <jani@nikula.org> wrote:\r
66 > We really have very few configuration options, and so far none of them\r
67 > are such that we could make the decision for the user. I think in this\r
68 > case pushing the responsibility to the user would be just *us* being\r
69 > paranoid. What does that tell our users?\r
70 >\r
71 > I also think the user should consider doing backups before upgrading\r
72 > notmuch in the first place. I am generally more concerned about the user\r
73 > doing a database dump of the old database version using the new notmuch\r
74 > than doing the upgrade. (Although in this case I think we're fine unless\r
75 > the user decides 'notmuch dump folder:important' is enough.)\r
76 \r
77 Sorry for the delay responding to this.\r
78 \r
79 I really think the right way to handle a database upgrade is:\r
80 \r
81 * fail notmuch new (with appropriate message) if run in quiet mode\r
82 * prompt user yes/no to upgrade database otherwise\r
83 \r
84 This will allow all users to acknowledge the upgrade and do the\r
85 appropriate thing, regardless of configuration, without adding a new\r
86 config option.\r
87 \r
88 jamie.\r
89 \r
90 --=-=-=\r
91 Content-Type: application/pgp-signature\r
92 \r
93 -----BEGIN PGP SIGNATURE-----\r
94 Version: GnuPG v1\r
95 \r
96 iQIcBAEBCAAGBQJTL3RHAAoJEO00zqvie6q8jjAP/i3572zTTmCNCNattzg5B9m3\r
97 AdeJPSFEEmLasQRVooqkigQpwiTGGGe8X2GaJpku+WXe9r9G4clW/CyNWFKOUQUJ\r
98 2zcAwaBNfIoDEM4B8xs/yDi8ZeCRugCdFhih1NdV3jmsSYcBS+iAwsMFtlNTuk6P\r
99 UYcWi8t75VLKTktTke0WHS6L+AYQFiT8fU86kLnyiUqcMCafycCpqlykPmiiSbaf\r
100 kkwzIVHJyRyiMn1+HL1+rOBbBX5Equ0P3Lpesqc6O2/73ouRxsUKCSeiosWQdFaB\r
101 uqE6le+/mhQQPB1SL4SPQjc2ZKOsidoMQ1l6o6UZS7wepzNKuaonIyzBG5RvF7VO\r
102 8UQAjBn7nE2jIFW/RmcxxOEQj8lEMax93MjNFJ5YBP7dVUO7BCOFiFo1BzyQF9qZ\r
103 C0o426s+YCTB5nKrSuP9l0uPVIrYh9P+ItWc5oiYp/S3kc8Ah6EioxqMe0LnTEwj\r
104 sf0s1nKDUudGo9dIGKeNSsi3DgzCObNViaK80WtIMI4xZCQyC00HQeZYo5nZSmFg\r
105 hf4kU13hy4/Sm9XmuhxD4v9Q0cazTNpGeQPHn5HZ3YSUUu1qYLAex4Rw3cgxjahL\r
106 3lAJPNfLsuy6nJrI5lP6e8+WtzC+0q+Ultb9v/7ntIuSwIXk7OuSULWDfjc7ynee\r
107 Kp26AARtkW4Mc8/ZDQDc\r
108 =ybEH\r
109 -----END PGP SIGNATURE-----\r
110 --=-=-=--\r