From ce178c7e1f7666bb40c4456a2ecee8122a668a99 Mon Sep 17 00:00:00 2001
From: naglis <827324+naglis@users.noreply.github.com>
Date: Thu, 16 Nov 2023 22:58:07 +0200
Subject: [PATCH] doc/protocol.rst: mention song id lifetime

---
 doc/protocol.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/protocol.rst b/doc/protocol.rst
index 214ab7520..9d28018c6 100644
--- a/doc/protocol.rst
+++ b/doc/protocol.rst
@@ -702,7 +702,8 @@ Song ids on the other hand are stable: an id is assigned to a song
 when it is added, and will stay the same, no matter how much it is
 moved around.  Adding the same song twice will assign different ids to
 them, and a deleted-and-readded song will have a new id.  This way, a
-client can always be sure the correct song is being used.
+client can always be sure the correct song is being used.  Song ids are not
+preserved across :program:`MPD` restarts.
 
 Many commands come in two flavors, one for each address type.
 Whenever possible, ids should be used.