<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib/index.cc, branch 0.15.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.15.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.15.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-12-24T23:02:22Z</updated>
<entry>
<title>_notmuch_message_index_file: unref (free) address lists from gmime.</title>
<updated>2012-12-24T23:02:22Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-12-11T03:33:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=47693539a64b884cbd9bffc9c832162848ad98f2'/>
<id>urn:sha1:47693539a64b884cbd9bffc9c832162848ad98f2</id>
<content type='text'>
Apparently as of GMime 2.4, you don't need to call
internet_address_list_destroy anymore, but you still need to call
g_object_unref (from the GMime Changelog).

On the medium performance corpus, valgrind shows "possibly lost"
leakage in "notmuch new" dropping from 7M to 300k.
</content>
</entry>
<entry>
<title>lib: Reject multi-message mboxes and deprecate single-message mbox</title>
<updated>2012-11-27T01:12:10Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-11-25T06:16:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=610f0e09929a5f351f7c1c3850ac7e0d83ffe388'/>
<id>urn:sha1:610f0e09929a5f351f7c1c3850ac7e0d83ffe388</id>
<content type='text'>
Previously, we would treat multi-message mboxes as one giant email,
which, besides the obvious incorrect indexing, often led to
out-of-memory errors for archival mboxes.  Now we explicitly reject
multi-message mboxes.  For historical reasons, we retain support for
single-message mboxes, but official deprecate this behavior.
</content>
</entry>
<entry>
<title>Convert non-UTF-8 parts to UTF-8 before indexing them</title>
<updated>2012-02-29T11:41:39Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2012-02-24T07:36:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=40edc971a82e236704216058591d4c7684f8058f'/>
<id>urn:sha1:40edc971a82e236704216058591d4c7684f8058f</id>
<content type='text'>
This fixes a bug that didn't allow to search for non-ASCII words such
parts. The code here was copied from show_text_part_content(), because
the show command already does the needed conversion when showing the
message.
</content>
</entry>
<entry>
<title>Ignore encrypted parts when indexing.</title>
<updated>2011-12-29T21:44:43Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-12-28T20:14:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ac7f84306474dbecea8f6fee2ef2e8d71cc950f7'/>
<id>urn:sha1:ac7f84306474dbecea8f6fee2ef2e8d71cc950f7</id>
<content type='text'>
It appears to be an oversight that encrypted parts were indexed
previously.  The terms generated from encrypted parts are meaningless
and do nothing but add bloat to the database.  It is not worth
indexing the encrypted content, just as it's not worth indexing the
signatures in signed parts.
</content>
</entry>
<entry>
<title>tag signed/encrypted during notmuch new</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-26T01:01:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1d6b49561f50d6cde1b473f9887e37748e49c02c'/>
<id>urn:sha1:1d6b49561f50d6cde1b473f9887e37748e49c02c</id>
<content type='text'>
This patch adds the tag "signed" to messages with any multipart/signed
parts, and the tag "encrypted" to messages with any
multipart/encrypted parts.  This only occurs when messages are indexed
during notmuch new, so a database rebuild is required to have old
messages tagged.
</content>
</entry>
<entry>
<title>Fix to index the "Re" term present in any subject.</title>
<updated>2010-11-24T02:11:04Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-11-24T02:11:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c7b4d15d0ad78b6f28b50310358ae255e6a08008'/>
<id>urn:sha1:c7b4d15d0ad78b6f28b50310358ae255e6a08008</id>
<content type='text'>
This was a misfeature where notmuch had extra code that just threw
away legitimate information. It was never indexing an initial "Re"
term in a subject. But some users have legitimately wanted to search
for this term.

The original code was written this way merely for strict compatiblity
with the indexing performed by sup, but we're not taking advantage of
that now anyway.
</content>
</entry>
<entry>
<title>lib: Add some missing static qualifiers.</title>
<updated>2010-11-02T04:58:43Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-11-02T04:58:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=67c3bc9db48c9e12d648df4792c706cae723676c'/>
<id>urn:sha1:67c3bc9db48c9e12d648df4792c706cae723676c</id>
<content type='text'>
These various functions and data are all used only locally, so should
be marked static. Ensuring we get these right will avoid us accidentally
leaking unintended symbols through the library interface.
</content>
</entry>
<entry>
<title>Do not segfault on empty mime parts</title>
<updated>2010-04-13T15:49:06Z</updated>
<author>
<name>martin f. krafft</name>
<email>madduck@madduck.net</email>
</author>
<published>2010-03-02T15:31:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=449a418c65fb1f9281f761aae23576900d0d3ef1'/>
<id>urn:sha1:449a418c65fb1f9281f761aae23576900d0d3ef1</id>
<content type='text'>
notmuch previously unconditionally checked mime parts for various
properties, but not for NULL, which is the case if libgmime encounters
an empty mime part.

Upon encounter of an empty mime part, the following is printed to
stderr (the second line due to my patch):

  (process:17197): gmime-CRITICAL **: g_mime_message_get_mime_part: assertion `GMIME_IS_MESSAGE (message)' failed
  Warning: Not indexing empty mime part.

This is probably a bug that should get addressed in libgmime, but for
not, my patch is an acceptable workaround.

Signed-off-by: martin f. krafft &lt;madduck@madduck.net&gt;
</content>
</entry>
<entry>
<title>Eliminate some useless gobject boilerplate.</title>
<updated>2010-02-05T01:26:00Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-05T01:26:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2bc0af15aa4cc5b4963e9ff2c2b615ea9ce4ffca'/>
<id>urn:sha1:2bc0af15aa4cc5b4963e9ff2c2b615ea9ce4ffca</id>
<content type='text'>
If we had external users of this filter then they might expect some of
these macros to exist. But since this is just internal, that's just
unneeded noise.
</content>
</entry>
<entry>
<title>notmuch new: Don't index uuencoded data.</title>
<updated>2010-02-05T01:08:11Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-05T01:08:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3767c6f9f9c4719f36569daa05cd56470b3fd00f'/>
<id>urn:sha1:3767c6f9f9c4719f36569daa05cd56470b3fd00f</id>
<content type='text'>
With modern MIME attachments, we're already avoiding indexing the
attachments. But for old-school uuencoded data in the mail, we have
been directly indexing the encoded data as terms, (which is not useful
at all---nobody will ever ytry to search based on the seemingly random
uuencoded data).

Additionally, indexing a modestly large uuencoded file seems to make
Xapian go insane, (consuming *lots* of memory).

We fix both problems by detecting uuencoded content and not performing
any indexing of it.
</content>
</entry>
</feed>
