<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch, branch 0.2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-04-16T20:20:22Z</updated>
<entry>
<title>make release: Add Debian package building and upload</title>
<updated>2010-04-16T20:20:22Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T20:13:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e6d20b7b8f47bcd5da14639c31a4943e188c070d'/>
<id>urn:sha1:e6d20b7b8f47bcd5da14639c31a4943e188c070d</id>
<content type='text'>
Finally, a single button to push to do all the uploading.
</content>
</entry>
<entry>
<title>Increment version to 0.2.</title>
<updated>2010-04-16T20:02:34Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T20:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3461aa8dc2139e734b65ec9a6e727178dfc8e799'/>
<id>urn:sha1:3461aa8dc2139e734b65ec9a6e727178dfc8e799</id>
<content type='text'>
Only minor features added this time--nothing that merits a 1.0.
</content>
</entry>
<entry>
<title>make release: Add a check that version and debian/changelog are consistent</title>
<updated>2010-04-16T20:00:35Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T20:00:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=80240877f836214e556f1ff75a058465a69f2dea'/>
<id>urn:sha1:80240877f836214e556f1ff75a058465a69f2dea</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Makefile: Avoid complaining about .first-build-message not existing</title>
<updated>2010-04-16T19:10:23Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T19:10:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9b065ff3b2d38b72accc98e283db0d81bf1047ed'/>
<id>urn:sha1:9b065ff3b2d38b72accc98e283db0d81bf1047ed</id>
<content type='text'>
This cleans up a few spurious warnings from the build.
</content>
</entry>
<entry>
<title>Fix final link of notmuch binary to use C compiler if possible.</title>
<updated>2010-04-16T18:51:56Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T18:51:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b068f1cc849910045ab11ac84419814b5d1727ee'/>
<id>urn:sha1:b068f1cc849910045ab11ac84419814b5d1727ee</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>debian: Remove watch file.</title>
<updated>2010-04-16T18:35:33Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T18:35:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=533b02945d28f2a31cc25a87d270b8e2a150310d'/>
<id>urn:sha1:533b02945d28f2a31cc25a87d270b8e2a150310d</id>
<content type='text'>
We're switching to a native package, where we build the upstream and
debian releases simultaneously, so there's no need for a watch file.
</content>
</entry>
<entry>
<title>debian: Switch to "3.0 (native)" source format.</title>
<updated>2010-04-16T18:34:48Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T18:32:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c75ab298d0000adc975756a4f57f731f8eb77096'/>
<id>urn:sha1:c75ab298d0000adc975756a4f57f731f8eb77096</id>
<content type='text'>
To keep lintian happy.
</content>
</entry>
<entry>
<title>Makefile: Fix conditionals to avoid calling git when no .git is present</title>
<updated>2010-04-16T18:34:48Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T18:24:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b8f0646931a391062ae58796dad53b70abe25e64'/>
<id>urn:sha1:b8f0646931a391062ae58796dad53b70abe25e64</id>
<content type='text'>
Otherwise, building from a tar-file snapshot or release caused a bunch
of error messages from unnecessary git invocations.
</content>
</entry>
<entry>
<title>Makefile: Add a top-level "make snapshot" target.</title>
<updated>2010-04-16T18:34:48Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T18:08:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c41a6bb786c3b57d342b77efcc40ae7b6af3020f'/>
<id>urn:sha1:c41a6bb786c3b57d342b77efcc40ae7b6af3020f</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Makefile: Rework the version checks slightly.</title>
<updated>2010-04-16T18:34:48Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-16T18:03:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5999ff8d3cce4512486353784f9dec5242196ec1'/>
<id>urn:sha1:5999ff8d3cce4512486353784f9dec5242196ec1</id>
<content type='text'>
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".
</content>
</entry>
</feed>
