unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH v2 2/3] database: add n_d_index_file (deprecates n_d_add_message)
Date: Wed, 23 Aug 2017 08:01:22 -0300	[thread overview]
Message-ID: <87lgmaeef1.fsf@tethera.net> (raw)
In-Reply-To: <20170817231426.9627-2-dkg@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> We need a way to pass parameters to the indexing functionality on the
> first index, not just on reindexing.  The obvious place is in
> notmuch_database_add_message.  But since modifying the argument list
> would break both API and ABI, we needed a new name.
>

Pushed 2 and 3, but with both amended to fix whitespace errors. Please
_do_ adjust your settings, this is not a test ;).

d

  reply	other threads:[~2017-08-23 11:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  5:47 [PATCH 1/3] lib: clarify description of notmuch_database_add_message Daniel Kahn Gillmor
2017-08-09  5:47 ` [PATCH 2/3] database: add n_d_index_file (deprecates n_d_add_message) Daniel Kahn Gillmor
2017-08-17 11:31   ` David Bremner
2017-08-17 23:14     ` [PATCH v2 1/3] lib: clarify description of notmuch_database_add_message Daniel Kahn Gillmor
2017-08-17 23:14       ` [PATCH v2 2/3] database: add n_d_index_file (deprecates n_d_add_message) Daniel Kahn Gillmor
2017-08-23 11:01         ` David Bremner [this message]
2017-09-17 20:53           ` Daniel Kahn Gillmor
2017-09-18 10:55             ` David Bremner
2017-08-17 23:14       ` [PATCH v2 3/3] reindex: drop notmuch_param_t, use notmuch_indexopts_t instead Daniel Kahn Gillmor
2017-08-20 12:10       ` [PATCH v2 1/3] lib: clarify description of notmuch_database_add_message David Bremner
2017-08-09  5:47 ` [PATCH 3/3] reindex: drop notmuch_param_t, use notmuch_indexopts_t instead Daniel Kahn Gillmor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgmaeef1.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).