Return-Path: <david@tethera.net>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id E49D6431FBF
	for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 14:19:36 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
	autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zZLDRBn1sH0i for <notmuch@notmuchmail.org>;
	Mon, 17 Mar 2014 14:19:29 -0700 (PDT)
Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by olra.theworths.org (Postfix) with ESMTPS id E9BF2431FBD
	for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 14:19:28 -0700 (PDT)
Received: from remotemail by yantan.tethera.net with local (Exim 4.80)
	(envelope-from <david@tethera.net>)
	id 1WPewO-0002xs-7M; Mon, 17 Mar 2014 18:19:24 -0300
Received: (nullmailer pid 22705 invoked by uid 1000); Mon, 17 Mar 2014
	21:19:19 -0000
From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, Jameson Graef Rollins
	<jrollins@finestructure.net>, Notmuch list <notmuch@notmuchmail.org>
Subject: Re: WARNING: database upgrade coming
In-Reply-To: <87a9cood0l.fsf@nikula.org>
References: <874n37a017.fsf@zancas.localnet>
	<87txawkam3.fsf@servo.finestructure.net> <87a9cood0l.fsf@nikula.org>
User-Agent: Notmuch/0.17+133~g5348d19 (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Mon, 17 Mar 2014 18:19:19 -0300
Message-ID: <87eh20v7zc.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Mar 2014 21:19:37 -0000

Jani Nikula <jani@nikula.org> writes:

>
> FWIW it should always be safe to interrupt the upgrade; I know we don't
> inform the user about this.
>

With that in mind, would it be reasonable/worthwhile to print a 5 second (or so)
countdown before running the upgrade? But then people who run it
non-interactively would still automagically get the upgrade, just 5
seconds later.

d