WARNING: database upgrade coming
Jameson Graef Rollins
jrollins at finestructure.net
Mon Mar 17 14:29:34 PDT 2014
On Mon, Mar 17 2014, David Bremner <david at tethera.net> wrote:
> Jani Nikula <jani at 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.
My vote would be that anything invasive like this should be done with an
explicit "OK" from the user. In otherwords, when a database upgrade is
due, non-interactive usage of notmuch new should fail until the user has
run notmuch new interactively and acknowledged that a db upgrade will be
happening and that they're ok with it.
jamie.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20140317/f714ef91/attachment.pgp>
More information about the notmuch
mailing list