)]}'
{
  "commit": "03ea7f05ec57c485ec353ccd67a5d651652fe607",
  "tree": "0673a0f7e982eacb2ebabadf1bc18ff0a64a5ed4",
  "parents": [
    "8f373f0aba4e631a3a3c42ddca0b6c466d3ef5e5"
  ],
  "author": {
    "name": "Thomas Haller",
    "email": "thaller@redhat.com",
    "time": "Sat Apr 26 19:58:31 2025 +0200"
  },
  "committer": {
    "name": "Thomas Haller",
    "email": "thaller@redhat.com",
    "time": "Mon Nov 03 14:23:34 2025 +0100"
  },
  "message": "xxxx\n\nThere is still at least one problem. If we wanted to support that\nanother thread can run g_object_run_dispose(), then GSignalGroup\nwould still race to call g_signal_handler_disconnect(). But disposing an\nobject will make those handler-ids invalid and an assertion will fail.\nThat is also a bug, so GSignalGroup still doesn\u0027t support\ng_object_run_dispose() on other threads.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "75511a0202ab29ff6651bafcf7388901470c5d40",
      "old_mode": 33188,
      "old_path": "gobject/gsignalgroup.c",
      "new_id": "d8b0345a6704c53bf97cefacc1fbb0eed0dd8ac6",
      "new_mode": 33188,
      "new_path": "gobject/gsignalgroup.c"
    }
  ]
}