diff --git a/da7274cd761d7867515d3ab8a4903e326be4d075 b/da7274cd761d7867515d3ab8a4903e326be4d075
index c73ebd6dd..d21373920 100644
--- a/da7274cd761d7867515d3ab8a4903e326be4d075
+++ b/da7274cd761d7867515d3ab8a4903e326be4d075
@@ -34,6 +34,24 @@
       "parentUuid": "eb69d5e7_dd631bbb",
       "revId": "da7274cd761d7867515d3ab8a4903e326be4d075",
       "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "0febe25e_e2ac144f",
+        "filename": "/COMMIT_MSG",
+        "patchSetId": 1
+      },
+      "lineNbr": 10,
+      "author": {
+        "id": 1000028
+      },
+      "writtenOn": "2024-02-27T16:32:23Z",
+      "side": 1,
+      "message": "In osmo-pcu there is the following mechanism: A BTS becomes active (bts-\u003eactive \u003d\u003d true) when pcu_rx_info_ind has run once. This means that osmo-bts has to send a valid info indication once and the BTS will be active. Then the text indications with the version in it cease.\n\nOn the osmo-bts side we can see in pcu_rx_txt_ind what happens when PCU_VERSION is received. In particular the following is done:\n\nregenerate_si3_restoctets(bts);\nregenerate_si4_restoctets(bts);\npcu_tx_si_all(bts);\n\nMy first idea was to cease the PCU_VERSION txt indications when pcu_rx_info_ind is received the first time, regardless whether the BTS becomes active or not. However, I was afraid to do that since I am not sure if this would break something. If you think this initial idea is safe to do, then I can give it a try (and test it of course)",
+      "parentUuid": "e63a2308_8f9f0b0a",
+      "revId": "da7274cd761d7867515d3ab8a4903e326be4d075",
+      "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
     }
   ]
 }
\ No newline at end of file