diff --git a/c19f8fe917eedc095dbbac03a629307ef7f93c5a b/c19f8fe917eedc095dbbac03a629307ef7f93c5a
index 31d1787b9..ac6b467af 100644
--- a/c19f8fe917eedc095dbbac03a629307ef7f93c5a
+++ b/c19f8fe917eedc095dbbac03a629307ef7f93c5a
@@ -35,6 +35,24 @@
       "revId": "c19f8fe917eedc095dbbac03a629307ef7f93c5a",
       "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
     },
+    {
+      "unresolved": false,
+      "key": {
+        "uuid": "75f1c51f_e5e2f42d",
+        "filename": "/COMMIT_MSG",
+        "patchSetId": 1
+      },
+      "lineNbr": 18,
+      "author": {
+        "id": 1000074
+      },
+      "writtenOn": "2024-04-04T11:03:47Z",
+      "side": 1,
+      "message": "This is super usual in projects such as linux kernel, see:\n\n    git log | grep \"^Fixes: \"\n    \nThis is useful to programatically find fixes for a commit you are eg. cherry-picking into another (stable) branch.\n\nI tend to use it when I\u0027m fixing some bug and the patch causing it is known.",
+      "parentUuid": "38ec6d3f_8a242e2c",
+      "revId": "c19f8fe917eedc095dbbac03a629307ef7f93c5a",
+      "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
+    },
     {
       "unresolved": true,
       "key": {