From 0b0f4c61f1d54eeb3a38ab04dd1757b527ae0179 Mon Sep 17 00:00:00 2001
From: Max Kellermann <max@musicpd.org>
Date: Mon, 12 Nov 2018 12:45:40 +0100
Subject: [PATCH] doc/protocol.rst: remove documentation about `==` matching
 substrings

I added this sentence in commit
5271e81ebe7ee88ad89cd49a5ddcd8a5e04ef7ae, but this was merely
documented the legacy status quo, which has always been undocumented
for old-style filters.

But for new filters, using "==" for sub strings was a surprising
"feature", which I removed in commit
ac0852b4e33033d73770c610154ddb242f6c1119.
---
 doc/protocol.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/protocol.rst b/doc/protocol.rst
index 27364b821..4818b55fb 100644
--- a/doc/protocol.rst
+++ b/doc/protocol.rst
@@ -152,10 +152,7 @@ of:
   ``VALUE`` in ``AlbumArtist``
   and falls back to ``Artist`` tags if
   ``AlbumArtist`` does not exist.
-  ``VALUE`` is what to find.  The
-  `find` commands specify an exact value
-  and are case-sensitive; the `search`
-  commands specify a sub string and ignore case.
+  ``VALUE`` is what to find.
 
 - ``(TAG =~ 'VALUE')`` and ``(TAG !~ 'VALUE')`` use a Perl-compatible
   regular expression instead of doing a simple string comparison.
@@ -189,6 +186,9 @@ of:
   be enclosed in parantheses, e.g. :code:`((artist == 'FOO') AND
   (album == 'BAR'))`
 
+The :command:`find` commands are case sensitive, which
+:command:`search` and related commands ignore case.
+
 Prior to MPD 0.21, the syntax looked like this::
 
  find TYPE VALUE