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.
This commit is contained in:
Austin Clements 2014-08-25 13:25:59 -04:00 committed by David Bremner
parent 523f06a0ad
commit 344e4c65a4
2 changed files with 2 additions and 3 deletions

View file

@ -1031,8 +1031,7 @@ notmuch_new_command (notmuch_config_t *config, int argc, char *argv[])
return EXIT_FAILURE; return EXIT_FAILURE;
} }
if (add_files_state.verbosity >= VERBOSITY_NORMAL) if (add_files_state.verbosity >= VERBOSITY_NORMAL)
printf ("Your notmuch database has now been upgraded to database format version %u.\n", printf ("Your notmuch database has now been upgraded.\n");
notmuch_database_get_version (notmuch));
} }
add_files_state.total_files = 0; add_files_state.total_files = 0;

View file

@ -33,7 +33,7 @@ test_expect_equal "$output" "\
Welcome to a new version of notmuch! Your database will now be upgraded. Welcome to a new version of notmuch! Your database will now be upgraded.
This process is safe to interrupt. This process is safe to interrupt.
Backing up tags to FILENAME Backing up tags to FILENAME
Your notmuch database has now been upgraded to database format version 2. Your notmuch database has now been upgraded.
No new mail." No new mail."
test_begin_subtest "tag backup matches pre-upgrade dump" test_begin_subtest "tag backup matches pre-upgrade dump"