thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fsqueeze-backports 2012-12-09T17:33:34Z 2012-12-09T17:33:34Z David Bremner bremner@debian.org 2012-11-13T01:54:16Z urn:sha1:fb50cc41fe6f508118697d65a44e8f742a466ca0 These are meant to be shared between notmuch-tag and notmuch-restore. The bulk of the routines implement a "tag operation list" abstract data type act as a structured representation of a set of tag operations (typically coming from a single tag command or line of input). 2012-12-08T13:26:29Z Peter Feigl craven@gmx.net 2012-12-06T21:12:11Z urn:sha1:fd3ffe35a2bf15676426235b809df915cd3473e4 This commit adds a structured output printer for Lisp S-Expressions. Later commits will use this printer in notmuch search, show and reply. The structure is the same as json, but: - arrays are written as lists: ("foo" "bar" "baaz" 1 2 3) - maps are written as p-lists: (:key "value" :other-key "other-value") - true is written as t - false is written as nil - null is written as nil [ whitespace changes by db ] 2012-10-31T19:53:01Z Jani Nikula jani@nikula.org 2012-10-30T20:32:36Z urn:sha1:af6b4b29f97b1f457bb7220491bf37536e1b9d7a 2012-09-05T11:34:01Z Tomi Ollila tomi.ollila@iki.fi 2012-09-04T14:49:13Z urn:sha1:69843dd6283f17656510f1aae197bc263f9633e1 Use new target release-checks in place of verify-version-debian, verify-version-python verify-version-manpage. This target executes devel/release-checks.sh which does all the verifications the three dropped targets did, and some more. 2012-08-12T19:28:08Z Austin Clements amdragon@MIT.EDU 2012-08-07T13:04:27Z urn:sha1:d41946ea781caaf9652d037caa5f65a93a199b80 The string buffer quoting functions in json.c have been superseded by the new sprinter interface and are no longer used. Remove them. 2012-08-03T00:10:15Z David Bremner bremner@debian.org 2012-08-02T12:30:31Z urn:sha1:719897cdc330a41c22271fded8d911035c275dec Create a variable DISTCLEAN which contains a list of things to clean in the distclean target (in addition to running the clean target). The deleted comment seems to be false these days, since we do create files during configuration. Use "rm -rf" here as well in case we want to add directories to DISTCLEAN. 2012-08-03T00:09:45Z David Bremner bremner@debian.org 2012-08-02T12:27:26Z urn:sha1:8a745d310f966194e82f12f6453f05cc877379d6 These extra directories cause problems for building on Debian twice in a row. In order to remove directories, we need to us "rm -rf" instead of "rm -f". So now we should be extra careful what we add to the variable CLEAN. 2012-07-24T12:26:59Z craven@gmx.net craven@gmx.net 2012-07-23T10:39:45Z urn:sha1:36522fca1cac6ca23c2c4c0280e3e20e96f7bfbb Using the new structured printer support in sprinter.h, implement sprinter_json_create, which returns a new JSON structured output formatter. The formatter prints output similar to the existing JSON, but with differences in whitespace (mostly newlines, --output=summary prints the entire message summary on one line, not split across multiple lines). Also implement a "structured" formatter for plain text that prints prefixed strings, to be used with notmuch-search.c plain text output. 2012-06-10T23:05:02Z Jameson Graef Rollins jrollins@finestructure.net 2012-05-26T18:45:41Z urn:sha1:e3be5afbad1bc7a10d9c38f2c2eb611f5ba3cccb This new structure, notmuch_crypto_t, keeps all relevant crypto contexts and parameters together, and will make it easier to pass the stuff around and clean it up. The name of the crypto context inside this new struct will change, to reflect that it is actually a GPG context, which is a sub type of Crypto context. There are other types of Crypto contexts (Pkcs7 in particular, which we hope to support) so we want to be clear. The new crypto.c contains functions to return the proper context from the struct for a given protocol (and initialize it if needed), and to cleanup a struct by releasing the crypto contexts. 2012-04-15T12:42:15Z Austin Clements amdragon@MIT.EDU 2012-04-11T20:38:39Z urn:sha1:cddc27034687e1c3bc52204314dfa46219b5d6f9 Previously, the makefile created dependency files in a separate, first pass. In particular, include-ing the dependency files would cause make to attempt to rebuild those files using the dependency-generation rules in the makefile. Unfortunately, this approach required obtuse rules and silently delayed the start of the build process (by quite a bit on a clean tree without any dependency files). Worse, this required the dependency files to themselves depend on all of the headers the source file depended on, which meant that, if a header file was removed, the depedency file could not be updated because of a missing dependency (!), which would cause make to silently fail. This patch eliminates the dependency generation rules and instead generates dependency files as a side-effect of the regular build rule. On the first build, we don't need to know the dependencies beforehand; the object file doesn't exist, so it will be built anyway. On subsequent builds, if a header file is updated, the dependency rules generated by the previous build will force a rebuild. If a source file is updated, the dependency rules may be stale, but it doesn't matter because the updated source file will force a rebuild. In the final case above, the stale dependency rules may refer to a header file that no longer exists but is also no longer needed. In order to prevent this from breaking the build, we also pass gcc the -MP option, which generates phony targets for every depended-on header file, so make won't complain if it can't find them during a later build.