unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Jani Nikula <jani@nikula.org>, David Bremner <david@tethera.net>,
	Jameson Graef Rollins <jrollins@finestructure.net>,
	Notmuch list <notmuch@notmuchmail.org>
Subject: Re: WARNING: database upgrade coming
Date: Tue, 18 Mar 2014 01:06:55 -0500	[thread overview]
Message-ID: <874n2w59c0.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <877g7so6kj.fsf@nikula.org>

Jani Nikula <jani@nikula.org> writes:

> Something like this? Just insert text that makes sense to the user. ;)

If you decide to go this route, I wonder if it might also be worth
adding the text about interruption being OK.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

  reply	other threads:[~2014-03-18  6:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09 15:01 WARNING: database upgrade coming David Bremner
2014-03-12 11:25 ` David Bremner
2014-03-17 17:17 ` Jameson Graef Rollins
2014-03-17 19:12   ` Jani Nikula
2014-03-17 21:19     ` David Bremner
2014-03-17 21:29       ` Jameson Graef Rollins
2014-03-23  2:26         ` conservative database upgrade control David Bremner
2014-03-23  2:26           ` [PATCH 1/2] config: add key database.upgrades David Bremner
2014-03-23 13:12             ` Jani Nikula
2014-03-23  2:26           ` [PATCH 2/2] notmuch-new: block database upgrades in default configuration David Bremner
2014-03-23 14:17             ` Jani Nikula
2014-03-23 14:35               ` David Bremner
2014-03-23 14:39                 ` David Bremner
2014-03-23 23:54               ` Jameson Graef Rollins
2014-03-17 21:31       ` WARNING: database upgrade coming Jani Nikula
2014-03-18  6:06         ` Rob Browning [this message]
2014-03-18  6:57           ` Tomi Ollila
2014-03-18 11:55             ` Stewart Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874n2w59c0.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=david@tethera.net \
    --cc=jani@nikula.org \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).