diff options
| author |  Austin Clements <amdragon@mit.edu> | 2014-08-25 13:25:59 -0400 |
|---|---|---|
| committer |  David Bremner <david@tethera.net> | 2014-08-30 10:40:41 -0700 |
| commit | 344e4c65a43e0755506e065ec001df8b1eae91f7 (patch) | |
| tree | abfae423765f6f9d44243502c6338fd487034b0f /notmuch-new.c | |
| parent | 523f06a0add737aa0577f43c319f069bc0ff10f3 (diff) | |
new: Don't report version after upgrade
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.
Diffstat (limited to 'notmuch-new.c')
| -rw-r--r-- | notmuch-new.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/notmuch-new.c b/notmuch-new.c index 56910056..ddf42c14 100644 --- a/notmuch-new.c +++ b/notmuch-new.c @@ -1031,8 +1031,7 @@ notmuch_new_command (notmuch_config_t *config, int argc, char *argv[]) return EXIT_FAILURE; } if (add_files_state.verbosity >= VERBOSITY_NORMAL) - printf ("Your notmuch database has now been upgraded to database format version %u.\n", - notmuch_database_get_version (notmuch)); + printf ("Your notmuch database has now been upgraded.\n"); } add_files_state.total_files = 0; |