new: Don't report version after upgrade
authorAustin Clements <amdragon@mit.edu>
Mon, 25 Aug 2014 17:25:59 +0000 (13:25 -0400)
committerDavid Bremner <david@tethera.net>
Sat, 30 Aug 2014 17:40:41 +0000 (10:40 -0700)
commit344e4c65a43e0755506e065ec001df8b1eae91f7
treeabfae423765f6f9d44243502c6338fd487034b0f
parent523f06a0add737aa0577f43c319f069bc0ff10f3
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.
notmuch-new.c
test/T530-upgrade.sh