thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.3.1 2010-04-16T20:20:22Z 2010-04-16T20:20:22Z Carl Worth cworth@cworth.org 2010-04-16T20:13:12Z urn:sha1:e6d20b7b8f47bcd5da14639c31a4943e188c070d Finally, a single button to push to do all the uploading. 2010-04-16T20:00:35Z Carl Worth cworth@cworth.org 2010-04-16T20:00:35Z urn:sha1:80240877f836214e556f1ff75a058465a69f2dea Eventually I'd like to automate this so that one or the other of these files is canonical and the other is generated from it. Until then, add this check to the release process to avoid a skewed release being shipped. 2010-04-16T19:10:23Z Carl Worth cworth@cworth.org 2010-04-16T19:10:23Z urn:sha1:9b065ff3b2d38b72accc98e283db0d81bf1047ed This cleans up a few spurious warnings from the build. 2010-04-16T18:51:56Z Carl Worth cworth@cworth.org 2010-04-16T18:51:56Z urn:sha1:b068f1cc849910045ab11ac84419814b5d1727ee On Linux, a C program that depends on a C library which in turn depends on a C++ can be linked with the C compiler, (avoiding a direct link from the program to the C++ runtime libraries). Other platforms with less fancy linkers need to use the C++ compiler for this linking. 2010-04-16T18:34:48Z Carl Worth cworth@cworth.org 2010-04-16T18:24:43Z urn:sha1:b8f0646931a391062ae58796dad53b70abe25e64 Otherwise, building from a tar-file snapshot or release caused a bunch of error messages from unnecessary git invocations. 2010-04-16T18:34:48Z Carl Worth cworth@cworth.org 2010-04-16T18:08:56Z urn:sha1:c41a6bb786c3b57d342b77efcc40ae7b6af3020f Useful for verifying that our tar-file creation works. The tar-file name can't easily be used as a target directly since it depends on the current git revision. 2010-04-16T18:34:48Z Carl Worth cworth@cworth.org 2010-04-16T18:03:25Z urn:sha1:5999ff8d3cce4512486353784f9dec5242196ec1 Theese were previously pointing to "make VERSION=X.Y release", but we've recently changed to an alternate scheme involving the updated version in a file named "version". 2010-04-16T18:34:48Z Carl Worth cworth@cworth.org 2010-04-16T17:37:32Z urn:sha1:b7dc24298dc69ffb62fd69cd735c0672b2e27dd2 We do this so that "git archive" produces a usable tar file without us having to post-modify it, (since tools like git-buildpackage might not give us an easy way to hook into the tar-file-creation step). To support this we also have to change our preference to prefer the git-described-based version (if available) and only if not available do we fallback to using what's in the "version" file. Finally, we also ovverride this preference when releasing, (where what's in the "version" file wins). Note that using our Makefile's rule to create a tar file still will insert the git-based version into the tar file. This is useful for creating snapshots which will correctly report the git version from which they were created. 2010-04-16T15:33:31Z Carl Worth cworth@cworth.org 2010-04-16T15:33:31Z urn:sha1:4906f6b9aec7947d609fe9127898e6a94dafd874 It's just too long for copy/paste, so just let the user know the name of the file containing the message instead. 2010-04-16T15:31:46Z Carl Worth cworth@cworth.org 2010-04-16T15:31:46Z urn:sha1:ff13111cf36298cde09e4ff85ec83fdd42b52f0a This was accidentally hard-coded to always print the 0.1 NEWS blurb.