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@notmuchmail.org
Subject: Re: [PATCH] lib: work around xapian bug with get_mset(0,0, x)
Date: Fri, 20 Apr 2018 09:53:23 -0300	[thread overview]
Message-ID: <87lgdi11ks.fsf@tethera.net> (raw)
In-Reply-To: <87sh7rqo7w.fsf@fifthhorseman.net>

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


> But if we want a compile-time check, i don't think we'd need anything
> fancier than something like (potentially even directly in query.cc):
>
>     #if XAPIAN_AT_LEAST(1,4,6)
>     #define MSET_GET_MIN_COUNT 0
>     #else
>     #define MSET_GET_MIN_COUNT 1
>     #endif
>
> what else were you thinking we'd need?
>
>      --dkg

I forgot about the XAPIAN_AT_LEAST macro. Nonetheless, I'm not keen to
ship untested/uncompiled code (no matter how "obviously correct" it is),
so I'd prefer to wait until Xapian 1.4.6 actually exists before adding
an ifdef like that. FWIW I doubt that the performance impact of passing
1 instead of 0 here is measurable. For me, getting a bug fix release out
is a matter of some urgency; fine tuning and testing against xapian
1.4.6 can wait.

d

  reply	other threads:[~2018-04-20 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 11:43 [PATCH] lib: work around xapian bug with get_mset(0,0, x) David Bremner
2018-04-15 16:54 ` Tomi Ollila
2018-04-18  0:07   ` [PATCH] NEWS: news item for mset fix David Bremner
2018-04-18  6:59     ` Tomi Ollila
2018-04-18 19:04 ` [PATCH] lib: work around xapian bug with get_mset(0,0, x) Daniel Kahn Gillmor
2018-04-18 23:13   ` David Bremner
2018-04-19 14:12     ` Daniel Kahn Gillmor
2018-04-20 12:53       ` David Bremner [this message]
2018-04-27  1:53 ` David Bremner
2018-04-27  1:53   ` David Bremner
2018-04-28 14:34 ` David Bremner

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=87lgdi11ks.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).