Re: WARNING: database upgrade coming

diff --git a/9e/151dee43f851baf3a69a0d2bb34d750d9d2ff1 b/9e/151dee43f851baf3a69a0d2bb34d750d9d2ff1
new file mode 100644 (file)
index 0000000..0a485a5
--- /dev/null
+++ b/9e/151dee43f851baf3a69a0d2bb34d750d9d2ff1
@@ -0,0 +1,70 @@
+Return-Path: <david@tethera.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 E49D6431FBF\r
+       for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 14:19:36 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       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 zZLDRBn1sH0i for <notmuch@notmuchmail.org>;\r
+       Mon, 17 Mar 2014 14:19:29 -0700 (PDT)\r
+Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id E9BF2431FBD\r
+       for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 14:19:28 -0700 (PDT)\r
+Received: from remotemail by yantan.tethera.net with local (Exim 4.80)\r
+       (envelope-from <david@tethera.net>)\r
+       id 1WPewO-0002xs-7M; Mon, 17 Mar 2014 18:19:24 -0300\r
+Received: (nullmailer pid 22705 invoked by uid 1000); Mon, 17 Mar 2014\r
+       21:19:19 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Jani Nikula <jani@nikula.org>, Jameson Graef Rollins\r
+       <jrollins@finestructure.net>, Notmuch list <notmuch@notmuchmail.org>\r
+Subject: Re: WARNING: database upgrade coming\r
+In-Reply-To: <87a9cood0l.fsf@nikula.org>\r
+References: <874n37a017.fsf@zancas.localnet>\r
+       <87txawkam3.fsf@servo.finestructure.net> <87a9cood0l.fsf@nikula.org>\r
+User-Agent: Notmuch/0.17+133~g5348d19 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Mon, 17 Mar 2014 18:19:19 -0300\r
+Message-ID: <87eh20v7zc.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\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 21:19:37 -0000\r
+\r
+Jani Nikula <jani@nikula.org> writes:\r
+\r
+>\r
+> FWIW it should always be safe to interrupt the upgrade; I know we don't\r
+> inform the user about this.\r
+>\r
+\r
+With that in mind, would it be reasonable/worthwhile to print a 5 second (or so)\r
+countdown before running the upgrade? But then people who run it\r
+non-interactively would still automagically get the upgrade, just 5\r
+seconds later.\r
+\r
+d\r
+\r
+\r
+\r
+\r