thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=master 2014-03-10T00:59:27Z 2014-03-10T00:59:27Z David Bremner david@tethera.net 2014-03-10T00:59:27Z urn:sha1:9b31c62680d6633d7d03cf416b593abfe02ced6d From now on, we should edit the rst source. 2013-12-31T00:34:23Z David Bremner david@tethera.net 2013-12-31T00:34:23Z urn:sha1:ceef57b3d95d3e4e1ea90001d99792626529dca3 2013-12-28T22:40:05Z David Bremner david@tethera.net 2013-12-28T22:40:05Z urn:sha1:05b534209d44b74105308e521dcac82a5e4afe43 Unfortunately release-checks.sh will whine a bit because it has not caught up with the renaming of the version macros. 2013-12-07T09:07:15Z David Bremner david@tethera.net 2013-12-07T09:02:08Z urn:sha1:bb390f89a1599f4767fbf7fc7cb1f01aba22b9ae Roll (one last?) release candidate because of Austin's LIBNOTMUCH_VERSION changes. Atomically bump the manually (NEWS, debian/changelog) and automatically (everywhere else) updated places version is mentioned. 2013-11-29T01:00:52Z David Bremner david@tethera.net 2013-11-29T01:00:52Z urn:sha1:6c9cd7d20c0b43d758d6256681a0b6015d17e983 2013-11-24T00:29:46Z David Bremner david@tethera.net 2013-11-20T23:42:00Z urn:sha1:bd0c56b2bdb10aa88b41ec9460f9e67a90d63c12 Various other files are synched using "make update-versions". NEWS has to be hand edited. 2013-08-17T07:06:08Z Austin Clements amdragon@MIT.EDU 2013-08-16T15:35:43Z urn:sha1:dc51bf0ad4ce84414e79d2f30752502f7c0d46c0 Previously, reply's default text format used an odd mix of RFC 2045 MIME encoding for the reply template's body and some made-up RFC 2822-like UTF-8 format for the headers. The intent was to present the headers to the user in a nice, un-encoded format, but this assumed that whatever ultimately sent the email would RFC 2047-encode the headers, while at the same time the body was already RFC 2045 encoded, so it assumed that whatever sent the email would *not* re-encode the body. This can be fixed by either producing a fully decoded UTF-8 reply template, or a fully encoded MIME-compliant RFC 2822 message. This patch does the latter because it is a) Well-defined by RFC 2822 and MIME (while any UTF-8 format would be ad hoc). b) Ready to be piped to sendmail. The point of the text format is to be minimal, so a user should be able to pop up the template in whatever editor they want, edit it, and push it to sendmail. c) Consistent with frontend capabilities. If a frontend has the smarts to RFC 2047 encode the headers before sending the mail, it probably has the smarts to RFC 2047 decode them before presenting the template to a user for editing. Also, as far as I know, nothing automated consumes the reply text format, so changing this should not cause serious problems. (And if anything does still consume this format, it probably gets these encoding issues wrong anyway.) 2013-08-03T11:29:40Z David Bremner bremner@debian.org 2013-08-03T11:29:40Z urn:sha1:48f2b3f1bc279f61b78d2cb4b19e8b05e607b125 man pages, NEWS, and debian changelog all hardcode date. Make them hardcode the same date. 2013-07-28T14:28:03Z David Bremner bremner@debian.org 2013-07-28T14:18:48Z urn:sha1:80b25792b2fdbb7f495556db360148798e224930 These are manually set in version and NEWS, and propagate to the other files via "make update-versions" 2013-06-29T22:28:18Z Peter Wang novalazy@gmail.com 2013-06-23T04:23:58Z urn:sha1:1e690347a7dab5ca3e10ea80b75a20de9205981d Add references to notmuch-insert.1 from other man pages.