On Wed, Jul 09 2014, David Bremner wrote:
> In order to support out of tree builds, generate `doc/config.dox` from
> configure.
>
> In order to avoid hardcoding version in doxygen.cfg, generate
> doc/version.dox at build time.
is this commit message accurate ?
> ---
> configure | 12 +
Peter Wang writes:
> From: Jani Nikula
>
> notmuch_database_close may fail in Xapian ->flush() or ->close(), so
> report the status. Similarly for notmuch_database_destroy which calls
> close.
pushed this one patch, along with a minimal NEWS item.
Tomi Ollila writes:
> So that $(VERSION) and version.stamp uses the git-describe -based
> version data instead of the content of `version' file.
pushed.
d
Peter Wang writes:
> This option causes notmuch insert to fail (with exit code 3) on failure
> to index the message, or failure to set the tags on the message, or if
> closing (flushing) the database fails. Failure to sync tags to flags
> has no effect.
I don't really understand why it's OK to
These tests deliver all possible (single-root) four-message threads in
all possible orders and check that notmuch successfully links them
into threads. These tests supersede and replace the previous and much
less thorough "T260-thread-order" tests.
There are two variants of the test: one delivers
Peter Wang writes:
> From: Jani Nikula
>
> notmuch_database_close may fail in Xapian ->flush() or ->close(), so
> report the status. Similarly for notmuch_database_destroy which calls
> close.
pushed this one patch, along with a minimal NEWS item.
___
Tomi Ollila writes:
> So that $(VERSION) and version.stamp uses the git-describe -based
> version data instead of the content of `version' file.
pushed.
d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Peter Wang writes:
> This option causes notmuch insert to fail (with exit code 3) on failure
> to index the message, or failure to set the tags on the message, or if
> closing (flushing) the database fails. Failure to sync tags to flags
> has no effect.
I don't really understand why it's OK to
These tests deliver all possible (single-root) four-message threads in
all possible orders and check that notmuch successfully links them
into threads. These tests supersede and replace the previous and much
less thorough "T260-thread-order" tests.
There are two variants of the test: one delivers
On Wed, Jul 09 2014, David Bremner wrote:
> In order to support out of tree builds, generate `doc/config.dox` from
> configure.
>
> In order to avoid hardcoding version in doxygen.cfg, generate
> doc/version.dox at build time.
is this commit message accurate ?
> ---
> configure | 12 +
10 matches
Mail list logo