From: Austin Clements <amdragon@MIT.EDU>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v3 03/13] new: Don't report version after upgrade
Date: Sat, 23 Aug 2014 18:59:45 -0400 [thread overview]
Message-ID: <20140823225945.GL3015@mit.edu> (raw)
In-Reply-To: <87siknjjvm.fsf@nikula.org>
Quoth Jani Nikula on Aug 23 at 6:39 pm:
> On Fri, 01 Aug 2014, Austin Clements <amdragon@MIT.EDU> wrote:
> > The version number has always been pretty meaningless to the user and
> > it's about to become even more meaningless with the introduction of
> > "features". Hopefully, the database will remain on version 3 for some
> > time to come; however, the introduction of new features over time in
> > version 3 will necessitate upgrades within version 3. It would be
> > confusing if we always tell the user they've been "upgraded to version
> > 3". If the user wants to know what's new, they should read the news.
>
> I think this is good for now.
>
> What do you think about adding notmuch_database_get_features(), and
> printing that?
Mark had a similar comment, so here's my reply:
id:20140727162426.GF13893@mit.edu
I'm happy with adding more transparency around this, though I'd prefer
to do it as follow-up to avoid expanding this series and because I'm
pretty sure adding something like notmuch_database_get_features
wouldn't require any non-trivial changes to the stuff in this series.
> BR,
> Jani.
next prev parent reply other threads:[~2014-08-23 22:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 2:09 [PATCH v3 00/13] Implement and use database "features" Austin Clements
2014-08-01 2:09 ` [PATCH v3 01/13] test: Include generated dependencies for test sources Austin Clements
2014-08-01 2:09 ` [PATCH v3 02/13] util: Const version of strtok_len Austin Clements
2014-08-06 13:43 ` David Bremner
2014-08-01 2:09 ` [PATCH v3 03/13] new: Don't report version after upgrade Austin Clements
2014-08-23 15:39 ` Jani Nikula
2014-08-23 22:59 ` Austin Clements [this message]
2014-08-24 12:56 ` Jani Nikula
2014-08-01 2:09 ` [PATCH v3 04/13] lib: Database version 3: Introduce fine-grained "features" Austin Clements
2014-08-23 16:02 ` Jani Nikula
2014-08-24 0:57 ` Austin Clements
2014-08-23 22:21 ` David Bremner
2014-08-24 0:58 ` Austin Clements
2014-08-24 3:58 ` David Bremner
2014-08-24 22:16 ` Austin Clements
2014-08-24 23:03 ` David Bremner
2014-08-01 2:09 ` [PATCH v3 05/13] test: Tool to build DB with specific version and features Austin Clements
2014-08-23 16:03 ` Jani Nikula
2014-08-01 2:09 ` [PATCH v3 06/13] test: Tests for future version and unknown feature handling Austin Clements
2014-08-01 2:09 ` [PATCH v3 07/13] lib: Simplify upgrade code using a transaction Austin Clements
2014-08-01 2:09 ` [PATCH v3 08/13] lib: Use database features to drive upgrade Austin Clements
2014-08-01 2:09 ` [PATCH v3 09/13] lib: Reorganize upgrade around document types Austin Clements
2014-08-01 2:10 ` [PATCH v3 10/13] lib: Report progress for combined upgrade operation Austin Clements
2014-08-01 2:10 ` [PATCH v3 11/13] lib: Support empty header values in database Austin Clements
2014-08-01 2:10 ` [PATCH v3 12/13] lib: Return an error from operations that require an upgrade Austin Clements
2014-08-01 2:10 ` [PATCH v3 13/13] lib: Update doc of notmuch_database_{needs_upgrade, upgrade} Austin Clements
2014-08-07 21:55 ` [PATCH v3 00/13] Implement and use database "features" Tomi Ollila
2014-08-08 18:18 ` Austin Clements
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=20140823225945.GL3015@mit.edu \
--to=amdragon@mit.edu \
--cc=jani@nikula.org \
--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).