thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.17-4 2013-12-07T02:31:19Z 2013-12-07T02:31:19Z Austin Clements amdragon@MIT.EDU 2013-12-04T16:19:46Z urn:sha1:3d4b0930bdc135d8f8edff1f29adb4d3ad0673ad This version of the library introduces LIBNOTMUCH_CHECK_VERSION and the *_VERSION macros. Bumping the version number is also necessary to make the comment on LIBNOTMUCH_CHECK_VERSION no longer a lie. 2013-12-07T02:31:11Z Austin Clements amdragon@MIT.EDU 2013-12-04T16:19:45Z urn:sha1:8fb16e277e4d6c32bafa79ae7967e1e6ba9258e0 This makes it clear that these macros refer to the *library* version, and not to the notmuch application-level release. Since there are no consumers of these macros yet, this is now or never. 2013-12-07T02:31:04Z Austin Clements amdragon@MIT.EDU 2013-12-04T16:19:44Z urn:sha1:4b14ccf0d66f52d4777c928a67cd55de9d3e748a We have two distinct "library version" numbers: the soname version and the version macros. We need both for different reasons: the version macros enable easy compile-time version detection (and conditional compilation), while the soname version enables runtime version detection (which includes the version checking done by things like the Python bindings). However, currently, these two version numbers are different, which is unnecessary and can lead to confusion (especially in things like Debian, which include the soname version in the package name). This patch makes them the same by bumping the version macros up to agree with the soname version. (We should probably keep the version number in just one place so they can't get out of sync, but that can be done in another patch.) 2013-11-27T11:43:29Z David Bremner david@tethera.net 2013-11-26T02:55:24Z urn:sha1:b9f0e6923d645a044f837d61a9343ea16d56504e Unfortunately old versions of GCC and clang do not provide byte order macros, so we re-invent them. If UTIL_BYTE_ORDER is not defined or defined to 0, we fall back to macros supported by recent versions of GCC and clang 2013-11-25T11:55:54Z David Bremner david@tethera.net 2013-11-24T21:29:42Z urn:sha1:20adfe39d7624150a5b337bb77a9647bb3def54b Previously PLATFORM_BYTE_ORDER and IS_LITTLE_ENDIAN were not defined, so the little endian code was always compiled in. This will have the effect that the "SHA1s" on big endian architectures will change (i.e. become actual sha1s). So someone re-indexing their database could conceivable lose tags on messages without a message-id header. 2013-11-20T00:15:02Z Tomi Ollila tomi.ollila@iki.fi 2013-11-14T22:03:27Z urn:sha1:2fd7ef64baf02892a7bebfb57d593afb086145ef The error messages written during the steps replacing old database with new now includes relevant paths and strerror. 2013-11-20T00:14:28Z Tomi Ollila tomi.ollila@iki.fi 2013-11-14T22:03:26Z urn:sha1:6452ae0fcb0a2ee45a47144da71a6de9d8dace2c In case previous notmuch compact has been interrupted there is old work-in-progress database compact directory partially filled. Remove it just before starting to fill the directory with new files. 2013-11-20T00:13:25Z Tomi Ollila tomi.ollila@iki.fi 2013-11-14T22:03:25Z urn:sha1:cb6cc296e27fdab85faa4bdd670eda2e0c53b8c2 It is less error prone and window of failure opportunity is smaller if the old (backup) database is always renamed (instead of sometimes rmtree'd) before new (compacted) database is put into its place. Finally rmtree() old database in case old database backup is not kept. 2013-11-18T00:25:43Z Tomi Ollila tomi.ollila@iki.fi 2013-11-13T17:02:44Z urn:sha1:19a89753ca20b269a131e747238925cce254c627 catch Xapian::Error in compact code in lib/database.cc to be consistent with other code in addition to not making software crash on uncaught other Xapian error. 2013-11-18T00:25:25Z Tomi Ollila tomi.ollila@iki.fi 2013-11-13T17:02:43Z urn:sha1:4d5986e8ad671c1f5504894af6fbe37ba314bed8 Notmuch compact code whitespace changes to match devel/STYLE.