<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T850-git.sh, branch nmweb</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=nmweb</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=nmweb'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2023-07-21T10:41:50Z</updated>
<entry>
<title>test: support testing notmuch as installed</title>
<updated>2023-07-21T10:41:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ec26eeaeec87781dee7dbf720103a5bc9b6bba5d'/>
<id>urn:sha1:ec26eeaeec87781dee7dbf720103a5bc9b6bba5d</id>
<content type='text'>
We put some effort into testing the built copy rather than some
installed copy. On the other hand for people like packagers, testing
the installed copy is also of interest.

When NOTMUCH_TEST_INSTALLED is set to a nonempty value, tests do not
require a built notmuch tree or running configure.

Some of the tests marked as broken when running against installed
notmuch are probably fixable.
</content>
</entry>
<entry>
<title>test: treat undefined feature variables as 0</title>
<updated>2023-07-21T09:58:16Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dfa43a19218ed46f677034ab7bf8b8907a327935'/>
<id>urn:sha1:dfa43a19218ed46f677034ab7bf8b8907a327935</id>
<content type='text'>
When running the test suite without building first, it is desirable to
have the tests consider these variables being undefined as equivalent
to the feature not being present, and in particular for the tests not
to generate errors.
</content>
</entry>
<entry>
<title>CLI/git: add --format-version argument to init subcommand</title>
<updated>2022-07-07T10:05:55Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-06-23T12:30:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bf5eacbe7e5b852e030e6a05469dbc9eae48535e'/>
<id>urn:sha1:bf5eacbe7e5b852e030e6a05469dbc9eae48535e</id>
<content type='text'>
This is primarily intended to support testing upward compatibility
with legacy repos.
</content>
</entry>
<entry>
<title>CL/git: add format version 1</title>
<updated>2022-07-07T09:56:05Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-06-23T12:30:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6219e7380ae34cc0c8142f4174bee3cde9bf9662'/>
<id>urn:sha1:6219e7380ae34cc0c8142f4174bee3cde9bf9662</id>
<content type='text'>
The original nmbug format (now called version 0) creates 1
subdirectory of 'tags/' per message. This causes problems for more
than (roughly) 100k messages.

Version 1 introduces 2 layers of hashed directories. This scheme was
chose to balance the number of subdirectories with the number of extra
directories (and git objects) created via hashing.

This should be upward compatible in the sense that old repositories
will continue to work with the updated notmuch-git.
</content>
</entry>
<entry>
<title>CLI/git: add safety checks for checkout and commit</title>
<updated>2022-06-17T11:40:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-05-14T18:25:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7d1e5a5348eb348a4e457650ca3b929e85efde70'/>
<id>urn:sha1:7d1e5a5348eb348a4e457650ca3b929e85efde70</id>
<content type='text'>
Commits or checkouts that modify a large fraction of the messages in
the database should be relatively rare (and in some automated process,
probably non-existent). For initial setup, where such operations are
expected, the user can pass --force.
</content>
</entry>
<entry>
<title>CLI/git: support configuration for repo location / prefix</title>
<updated>2022-06-17T11:40:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-05-10T10:32:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=99e85823c8de570c0f91bca44efa2c47cddb3cbf'/>
<id>urn:sha1:99e85823c8de570c0f91bca44efa2c47cddb3cbf</id>
<content type='text'>
This is probably more convenient than always passing a command line
argument.

Use notmuch-config for consistency with other notmuch CLI tools.

Now that there is something relevant in the config files, test the
--config option.
</content>
</entry>
<entry>
<title>CLI/git: change defaults for repo and prefix</title>
<updated>2022-06-17T11:40:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-05-07T13:32:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8ed68c1bbe8c1b7bb69d7bea1e0c8919bfcb0d0a'/>
<id>urn:sha1:8ed68c1bbe8c1b7bb69d7bea1e0c8919bfcb0d0a</id>
<content type='text'>
The previous defaults were not suitable for personal (i.e. not
bugtracking for notmuch development) use.

Provide two ways for the user to select nmbug compatible defaults;
command line argument and checking the name of the script.
</content>
</entry>
<entry>
<title>CLI/git: cache git indices</title>
<updated>2022-06-17T11:40:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-04-19T11:32:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=66ccf420c20bedec8dd78dc81ed1166761b7a467'/>
<id>urn:sha1:66ccf420c20bedec8dd78dc81ed1166761b7a467</id>
<content type='text'>
If the private index file matches a previously known revision of the
database, we can update the index incrementally using the recorded
lastmod counter. This is typically much faster than a full update,
although it could be slower in the case of large changes to the
database.

The "git-read-tree HEAD" is also a bottleneck, but unfortunately
sometimes is needed. Cache the index checksum and hash to reduce the
number of times the operation is run. The overall design is a
simplified version of the PrivateIndex class.
</content>
</entry>
<entry>
<title>CLI/git: replace enumeration of tags with sexp query.</title>
<updated>2022-06-17T11:40:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-04-10T17:22:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f67d7c9e7a2d110e54609e572c35804f0172ba11'/>
<id>urn:sha1:f67d7c9e7a2d110e54609e572c35804f0172ba11</id>
<content type='text'>
Unlike the (current) infix query parser provided by Xapian, the
notmuch specific sexp query parser supports prefixed wildcard queries,
so use those. In addition to being somewhat faster, this avoids
needing to escape all of the user's tags to pass via the shell.
</content>
</entry>
<entry>
<title>test/git: add known broken test for tag with quotes.</title>
<updated>2022-06-17T11:40:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-04-10T17:06:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b355973abcbe16875e717b8df28a3c1b8d424fb7'/>
<id>urn:sha1:b355973abcbe16875e717b8df28a3c1b8d424fb7</id>
<content type='text'>
There is current insufficient sanitization and/or escaping of tag names
internally in notmuch-git.
</content>
</entry>
</feed>
