Re: WARNING: database upgrade coming

diff --git a/4f/801bcd7ef4b61e8cbda91ddbfd5a72db92a317 b/4f/801bcd7ef4b61e8cbda91ddbfd5a72db92a317
new file mode 100644 (file)
index 0000000..6672b68
--- /dev/null
+++ b/4f/801bcd7ef4b61e8cbda91ddbfd5a72db92a317
@@ -0,0 +1,105 @@
+Return-Path: <jrollins@finestructure.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 3DF6A431FBD\r
+       for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 10:18:22 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id NKvCtYNp6n+J for <notmuch@notmuchmail.org>;\r
+       Mon, 17 Mar 2014 10:18:14 -0700 (PDT)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 73F62431FC0\r
+       for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 10:18:00 -0700 (PDT)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id 04003328085;\r
+       Mon, 17 Mar 2014 10:17:59 -0700 (PDT)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (unknown [198.129.209.100])\r
+       (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id 367972E509A4;\r
+       Mon, 17 Mar 2014 10:17:59 -0700 (PDT)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id A111060123; Mon, 17 Mar 2014 10:17:58 -0700 (PDT)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: David Bremner <david@tethera.net>, Notmuch list <notmuch@notmuchmail.org>\r
+Subject: Re: WARNING: database upgrade coming\r
+In-Reply-To: <874n37a017.fsf@zancas.localnet>\r
+References: <874n37a017.fsf@zancas.localnet>\r
+User-Agent: Notmuch/0.17+134~g31849a1 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Mon, 17 Mar 2014 10:17:56 -0700\r
+Message-ID: <87txawkam3.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 17 Mar 2014 17:18:23 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+On Sun, Mar 09 2014, David Bremner <david@tethera.net> wrote:\r
+> I will fairly soon push some version of jani's patches changing folder:\r
+> matching to master. This will require an irreversible database upgrade.\r
+>\r
+> Of course we believe everything is going to go smoothly, but you\r
+> probably should not run this upcoming version of notmuch on your live\r
+> mail store until you understand the implications for your workflow.\r
+>\r
+> It never hurts to backup your tags before upgrading notmuch. We've never\r
+> had a data loss yet, but it _is_ software.\r
+\r
+Hey, David et. al.  I recently did an upgrade to notmuch/master after\r
+being out of the loop for a while and not noticing that a database\r
+upgrade was pending.  The next notmuch new informed me that a database\r
+upgrade was required, but it went ahead and did the upgrade unprompted.\r
+Things went fine, but it did worry me a bit that I didn't know an\r
+upgrade was pending and didn't have a chance to do a backup before it\r
+happened.\r
+\r
+It would be nice if notmuch new would prompt users when an database\r
+upgrade is pending, to give the user an option to abort before\r
+proceeding so that they can do a backup if they'd like.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1\r
+\r
+iQIcBAEBCAAGBQJTJy5EAAoJEO00zqvie6q8xcEP/it8Ary57DBggKigBlevTwha\r
+m4WoqXDafNlWnD4VwFWIO5u3gMpw1hqrYrqJZRBMvNhxmvS1ZIVTXO6fGaSX/eZf\r
+FdcAWD3LY+ejxJf3nrqErF1jt7e3X2C6K51pBZsj0BCcrOn8pmaNh77S6LqoHWcZ\r
+S0Jbs+ErPURFRDy+9QMmrMBM4/tUispCR01IweKownGD66ECfzfybj7MyZGyaTSA\r
+IrsiPtGFDWGdi87Bz9/3c1526yfcRFW6VIDd59qxqKO8f7swqHE7mTxmm6eNaDzb\r
+O74xj4gcoxDMQzmvZFppEqYLhoOKRYcGZZ+STaQ2oMFkuchohe06nqJaDQPmZ6QO\r
+Qo8XY+ep7r8aC5+EPFUAmb38bPLvVtlMRC759ITANmwDTBpDLm7hg4O2vtnF7a3x\r
+lPSl6f01TxFEE93fhIqnfygKC37ydgh1xGYSMFf3eKOjoflt6tva0RSfXlQYdd+m\r
++BNZg/dyFck3oo0E6oEUiqlkOG+baOKWkFh/bdOgaPSnQHobviraEii5aN8OoKQk\r
+zq9q9tZLDrtur6CX0GPPjXBsVDja9ipj2z+fH4ku3PaDf7UhDtu32ddXJEYu4Dt2\r
+YIeu1nC+BCHcWtzFupcN1nM4gX+lSIpIJONHzhpz5zF+hGDSgiIQVIqgR6rTlNkb\r
+KviaH1ubwSQPL5zFp7VS\r
+=jEYa\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r