<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/index.cc, branch master</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=master</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2009-11-10T00:24:03Z</updated>
<entry>
<title>libify: Move library sources down into lib directory.</title>
<updated>2009-11-10T00:24:03Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-10T00:12:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=146549321044615d9aef2b30cedccda9c49f3f38'/>
<id>urn:sha1:146549321044615d9aef2b30cedccda9c49f3f38</id>
<content type='text'>
A "make" invocation still works from the top-level, but not from
down inside the lib directory yet.
</content>
</entry>
<entry>
<title>index: Don't bother indexing quoted portions of messages (and signatures).</title>
<updated>2009-10-28T22:41:42Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-28T22:41:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=56218ddbb4a72fdec534773f2bd4e85aec914ae9'/>
<id>urn:sha1:56218ddbb4a72fdec534773f2bd4e85aec914ae9</id>
<content type='text'>
Our old notmuch-index-message.cc code had this, but I originally
left it out when adding indexing back in. I was concerned primarily
with mistakenly detecting signature markers and omitting important
text, (for example, I often do long lines of "----" as section
separators).

But now I  see that there's a performance benefit to skippint the
quotations, (about 120 files/sec. instead of 95 files/sec.). I mitigated
the bogus signature checking by recognizing nothing other than the
all-time classic "-- ".
</content>
</entry>
<entry>
<title>index: Store "Full Name &lt;user@example.com&gt;" addressses in the database</title>
<updated>2009-10-28T20:09:08Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-28T20:09:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3a91df21caddd952fe9a3e3ba8128e781a3f6ec5'/>
<id>urn:sha1:3a91df21caddd952fe9a3e3ba8128e781a3f6ec5</id>
<content type='text'>
We put these is as a separate term so that they can be extracted.
We don't actually need this for searching, since typing an email
address in as a search term will already trigger a phrase search
that does exactly what's wanted.
</content>
</entry>
<entry>
<title>Add full-text indexing using the GMime library for parsing.</title>
<updated>2009-10-28T19:50:10Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-28T17:42:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f9bbd7baa07110c7f345c8413e2426d00382cb1c'/>
<id>urn:sha1:f9bbd7baa07110c7f345c8413e2426d00382cb1c</id>
<content type='text'>
This is based on the old notmuch-index-message.cc from early in
the history of notmuch, but considerably cleaned up now that
we have some experience with Xapian and know just what we want
to index, (rather than just blindly trying to index exactly
what sup does).

This does slow down notmuch_database_add_message a *lot*, but I've
got some ideas for getting some time back.
</content>
</entry>
</feed>
