notmuch/lib/message-id.c, branch 0.34 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.34 2019-06-14T10:41:27Z lib: run uncrustify 2019-06-14T10:41:27Z uncrustify david@tethera.net 2019-06-13T10:55:35Z urn:sha1:2b62ca2e3b786beca8d89fa737bda0b49faa638d This is the result of running $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc in the lib directory lib: add _notmuch_message_id_parse_strict 2018-09-06T11:07:13Z David Bremner david@tethera.net 2018-08-30T11:29:14Z urn:sha1:b31e44c678bf3bfe81bcc5f159e627551f12700f The idea is that if a message-id parses with this function, the MUA generating it was probably sane, and in particular it's probably safe to use the result as a parent from In-Reply-to. lib: factor out message-id parsing to separate file. 2017-08-02T01:17:47Z David Bremner david@tethera.net 2017-06-04T12:32:26Z urn:sha1:2f94b3090c03bb56b43c4adfb94f7eeb28a6bf18 This is really pure C string parsing, and doesn't need to be mixed in with the Xapian/C++ layer. Although not strictly necessary, it also makes it a bit more natural to call _parse_message_id from multiple compilation units.