From: Jani Nikula <jani@nikula.org>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: automatic database upgrades (was: Re: [PATCH 0/7] cli: notmuch new improvements)
Date: Sat, 25 Jan 2014 21:29:55 +0200 [thread overview]
Message-ID: <87d2jfg8r0.fsf@nikula.org> (raw)
In-Reply-To: <87fvoc9dd7.fsf@qmul.ac.uk>
On Sat, 25 Jan 2014, Mark Walters <markwalters1009@gmail.com> wrote:
> What about a config option? Something like
> database_auto_upgrade=true/false? I wouldn't have a strong preference
> which was the default (though I would choose "false" in my own
> config). I guess we would need a command line --upgrade to allow people
> with database_auto_upgrade=false to do force/allow the upgrade.
I just recently read [1] again, I think it's a good one.
It makes me ask the question, why should we ask the user to make that
decision? The decision of what to do with the config option, or even
whether to upgrade the database or not. Basically the decision is made
when the user decides to upgrade notmuch. Once the user has upgraded
notmuch his choices are to upgrade the database or downgrade notmuch.
The user would probably just like to get on with the mail reading, which
is probably also just means to an end!
BR,
Jani.
[1] http://www.joelonsoftware.com/uibook/chapters/fog0000000059.html
next prev parent reply other threads:[~2014-01-25 19:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 20:32 [PATCH 0/7] cli: notmuch new improvements Jani Nikula
2014-01-19 20:32 ` [PATCH 1/7] cli: extract single message addition in notmuch new to clarify code Jani Nikula
2014-01-19 20:32 ` [PATCH 2/7] cli: only check the ignore list if needed Jani Nikula
2014-01-19 20:32 ` [PATCH 3/7] cli: use dirent_type in count_files too Jani Nikula
2014-01-19 20:32 ` [PATCH 4/7] cli: for loop is more customary Jani Nikula
2014-01-19 20:32 ` [PATCH 5/7] cli: abstract notmuch new result printing Jani Nikula
2014-01-19 20:32 ` [PATCH 6/7] cli: add --quiet option to notmuch new Jani Nikula
2014-01-24 8:58 ` Mark Walters
2014-01-24 9:54 ` Jani Nikula
2014-01-19 20:32 ` [PATCH 7/7] man: document notmuch new --quiet option Jani Nikula
2014-01-25 8:38 ` [PATCH 0/7] cli: notmuch new improvements Mark Walters
2014-01-25 14:59 ` automatic database upgrades (was: Re: [PATCH 0/7] cli: notmuch new improvements) Jani Nikula
2014-01-25 17:32 ` Mark Walters
2014-01-25 19:29 ` Jani Nikula [this message]
2014-01-25 17:29 ` [PATCH 0/7] cli: notmuch new improvements Tomi Ollila
2014-01-26 14:06 ` David Bremner
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=87d2jfg8r0.fsf@nikula.org \
--to=jani@nikula.org \
--cc=markwalters1009@gmail.com \
--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).