Message-ID: <4E1A6C7A.8060103@fifthhorseman.net>
Date: Sun, 10 Jul 2011 23:22:34 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11
MIME-Version: 1.0
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] debian: strictly depend on the same version of libnotmuch
References: <1310239029-13509-1-git-send-email-ukleinek@strlen.de>
	<87pqlifgad.fsf@zancas.localnet>	<4E1A15B3.6060200@fifthhorseman.net>
	<87wrfpee6x.fsf@zancas.localnet>
In-Reply-To: <87wrfpee6x.fsf@zancas.localnet>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig9E006480BD5762AB4924E8CF"
Precedence: list
Reply-To: notmuch@notmuchmail.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9E006480BD5762AB4924E8CF
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 07/10/2011 10:36 PM, David Bremner wrote:
>> This suggests to me that we may need to be bumping the SONAME when the=

>> query string format changes, no?
>=20
> If we follow the same rules as with symbols, then only when it breaks
> backwards compatability.

Right, but what breaks backwards compatibility in a string-based indexer?=


If the query "foo bar:baz" is interpreted as a search for two separate
simple strings, and then an update treats the "bar:" suffix specially,
is that backwards-incompatible because the semantics of the identical
search change?

The only way i can currently imagine "backwards compatibility" is if
version X has a set of query strings which all return some kind of "not
implemented" error value, and then version X+1 returns a legitimate
response for some subset of those same query strings.

Otherwise, each change in query string syntax actively modifies (in a
non-backwards-compatible way) the semantics of some part of the interface=
=2E

Is there some other way to view this distinction?

	--dkg


--------------enig9E006480BD5762AB4924E8CF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQJ8BAEBCgBmBQJOGmx6XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpEDYQAIBDUqW/O1z9jCeUX4x/xjfw
3Pbod8nhdy8N2J0tb6GOJufvdxh4LzgShxgR3PBhuSvRhLH7P1tsXasg+XHrio/1
U+bTRzUleIFKupZx3QDnqZhJA09O1ji8yNPJbztYmeJeUeRNfPwfZnSJaG7O+a9L
d8RT91NCdHh9gLYsWLtrLisw/XNhE288cSjsG1k/5w9FJMIKsTMW6GkVXs/6PK1L
GDzON3/7U8WC99BzrJfyui2o2v+ulHTWB+txBXEDyDVJaJ0idP+lL0Z8VhIEtFg8
oJYitZw3BuMrI7IYC1KHjTlDvwU+RyxaH733MZZOcwZDpx6M9flceak6pZd1EnOe
j3uVKT+Ll+WEEzjIYr6fY1Vy3n6sHXDRBJQORYZkQ4s1s2Cva0T/w/vql00P9Jbh
N31NhKysPxZpvqLZXPgXmRK20ugHQay3mMQMg7m/9xjA66+K+ujuj6bArw195JqT
NliQG7qolDDS3oiFsodMPJ21aACoUTVrIFg6Lta2g9SVAgGmFMShmrvuXwdag0zU
ORWaS4OzPzkvmMRFaRPOa5lwiJbjTqxRDV44Knx6G7PXyeRh33qqzfPS1Kazv9vr
XRDZ0kVKProwDS58aioR+7CHoZWPcXtyPFwk7EfSEXXCavbTZSHjo24HP+3l7p9U
mXmNCVREX8m8iynFhH3P
=m1sZ
-----END PGP SIGNATURE-----

--------------enig9E006480BD5762AB4924E8CF--