<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-restore.c, branch 0.3</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.3</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.3'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-03-09T17:22:29Z</updated>
<entry>
<title>lib: Rename iterator functions to prepare for reverse iteration.</title>
<updated>2010-03-09T17:22:29Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-03-09T17:22:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e5d2f22db290a830c0267f34b519c6138af00ed'/>
<id>urn:sha1:4e5d2f22db290a830c0267f34b519c6138af00ed</id>
<content type='text'>
We rename 'has_more' to 'valid' so that it can function whether
iterating in a forward or reverse direction. We also rename
'advance' to 'move_to_next' to setup parallel naming with
the proposed functions 'move_to_first', 'move_to_last', and
'move_to_previous'.
</content>
</entry>
<entry>
<title>notmuch restore: Don't waste time with messages with unchanged tags.</title>
<updated>2010-02-06T01:29:56Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-06T01:29:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=069cb5a73ac2487930baa75a9cd2850968361a16'/>
<id>urn:sha1:069cb5a73ac2487930baa75a9cd2850968361a16</id>
<content type='text'>
It's a simple optimization to look at a message and check that the
existing tags are actually different than the tags we are setting
before we do anything.

For my mail store this takes a "notmuch restore" that does nothing
from about 10 minutes down to 1 minute, so there's a significant
speedup here.
</content>
</entry>
<entry>
<title>Rename NOTMUCH_DATABASE_MODE_WRITABLE to NOTMUCH_DATABASE_MODE_READ_WRITE</title>
<updated>2009-11-21T21:10:18Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-21T21:10:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=637f99d8f3f45867d0a856503f9f302333824c07'/>
<id>urn:sha1:637f99d8f3f45867d0a856503f9f302333824c07</id>
<content type='text'>
And correspondingly, READONLY to READ_ONLY.
</content>
</entry>
<entry>
<title>Permit opening the notmuch database in read-only mode.</title>
<updated>2009-11-21T21:04:49Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2009-11-21T19:54:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f379aa52845f5594aa6cc2e7cf131d5f57202bbf'/>
<id>urn:sha1:f379aa52845f5594aa6cc2e7cf131d5f57202bbf</id>
<content type='text'>
We only rarely need to actually open the database for writing, but we
always create a Xapian::WritableDatabase. This has the effect of
preventing searches and like whilst updating the index.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Acked-by: Carl Worth &lt;cworth@cworth.org&gt;
</content>
</entry>
<entry>
<title>notmuch restore was skipping entries with no new tags</title>
<updated>2009-11-16T20:03:05Z</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2009-11-16T19:53:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c004e1e04b9d1b80ea65b26d65a9ec20641cc64c'/>
<id>urn:sha1:c004e1e04b9d1b80ea65b26d65a9ec20641cc64c</id>
<content type='text'>
notmuch restore used to only add tags; now that it clears existing
tags, it needs to operate on messages even if the new tag list is empty.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
Reviewed-by: Carl Worth &lt;cworth@cworth.org&gt;:

I fixed up the indentation here, (someday we might switch to 8-space
indents, but we haven't yet).
</content>
</entry>
<entry>
<title>Unbreak several notmuch commands after the addition of configuration.</title>
<updated>2009-11-12T04:29:30Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-12T04:29:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=13569ad6c96c3f3a653ac51274056614647ad7ef'/>
<id>urn:sha1:13569ad6c96c3f3a653ac51274056614647ad7ef</id>
<content type='text'>
All of the following commands:

	notmuch dump
	notmuch reply
	notmuch restore
	notmuch search
	notmuch show
	notmuch tag

were calling notmuch_database_open with an argument of NULL. This was
a legitimate call until the recent addition of configuration, after
which it is expected that all commands will lookup the correct path in
the configuration file. So fix all these commands to do that.

Also, while touching all of these commands, we fix them to use the
talloc context that is passed in rather than creating a local talloc
context. We also switch from using goto for return values, to doing
direct returns as soon as an error is detected, (which can be leak
free thanks to talloc).
</content>
</entry>
<entry>
<title>notmuch: Break notmuch.c up into several smaller files.</title>
<updated>2009-11-10T20:03:05Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-10T20:03:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=50144f95cababfb73027ca95ad1fb303c235a893'/>
<id>urn:sha1:50144f95cababfb73027ca95ad1fb303c235a893</id>
<content type='text'>
Now that the client sources are alone here in their own directory,
(with all the library sources down inside the lib directory), we can
break the client up into multiple files without mixing the files up.
The hope is that these smaller files will be easier to manage and
maintain.
</content>
</entry>
</feed>
