notmuch/lib/thread.cc, branch debian/0.38.3-3

lib/thread: add common prefix to debug messages, join lines

2021-05-23T11:01:38Z

This will simplify filtering these message, e.g. in the test suite.

lib: run uncrustify

2021-03-13T12:45:34Z

This is the result of running $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc in the lib directory

lib/thread: replace use of deprecated notmuch_message_get_flag

2020-07-18T14:03:29Z

This adds one more reason why _notmuch_thread_create might return NULL, but those were not previously enumerated, so no promises are broken.

lib: run uncrustify

2019-06-14T10:41:27Z

This is the result of running $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc in the lib directory

lib: cache user prefixes in database object

2019-05-25T10:08:20Z

This will be used to avoid needing a database access to resolve a db prefix from the corresponding UI prefix (e.g. when indexing). Arguably the setup of the separate header map does not belong here, since it is about indexing rather than querying, but we currently don't have any other indexing setup to do.

gmime-cleanup: pass NULL arguments explicitly where GMime 3.0 expects it

2019-05-03T09:57:27Z

Several GMime 2.6 functions sprouted a change in the argument order in GMime 3.0. We had a compatibility layer here to be able to handle compiling against both GMime 2.6 and 3.0. Now that we're using 3.0 only, rip out the compatibility layer for those functions with changed argument lists, and explicitly use the 3.0 argument lists. Signed-off-by: Daniel Kahn Gillmor

lib/thread: change _resolve_thread_relationships to use depths

2018-09-06T11:07:13Z

We (finally) implement the XXX comment. It requires a bit of care not to reparent all of the possible toplevel messages. _notmuch_messages_has_next is not ready to be a public function yet, since it punts on the mset case. We know in the one case it is called, the notmuch_messages_t is just a regular list / iterator.

lib/thread: rewrite _parent_or_toplevel to use depths

2018-09-06T11:07:13Z

This is part 1/2 of changing the reparenting of alleged toplevel messages to use a "deep" reference rather than just the first one found.

lib/thread: initial use of references as for fallback parenting

2018-09-06T11:07:13Z

This is mainly to lay out the structure of the final code. The problem isn't really solved yet, although some very simple cases are better (hence the fixed test). We need two passes through the messages because we need to be careful not to re-parent too many messages and end up without any toplevel messages.

use EMPTY_STRING in _parent_via_in_reply_to

2018-09-06T11:07:13Z

This is a review suggestion [1] of Tomi. I decided not to squash it so that the code movement remains clear. [1]: id:m2pnxxgf5q.fsf@guru.guru-group.fi