)]}'
{
  "commit": "9dbce799e7087a75851ba1ae321b22c19b6f75c3",
  "tree": "3b42bb4e9d38f6ef2d5bda9cfe08adb8f4575158",
  "parents": [
    "8b61adae4e25d9f6ec17462ac2b6f7ad6b5bab14"
  ],
  "author": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Wed Jul 08 16:09:48 2026 +0200"
  },
  "committer": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Tue Jul 14 10:58:15 2026 +0200"
  },
  "message": "qom: Fix device-list-properties \u0026 friends to show legacy-FOO props\n\nqmp_device_list_properties() skips properties whose name starts with\n\"legacy-\".  This is a flawed test for \"is a legacy property\".\n\nThe test is flawed because non-legacy properties can and do start with\n\"legacy-\".  Back when it was added, no such properties existed.  Right\nnow, three such properties do: property \"legacy-cmb\" of device \"nvme\",\nand properties \"legacy-cache\" and \"legacy-multi-node\" of devices\n\"x86_64-cpu\", \"i386-cpu\", and its children.\n\nThis affects QMP command \"device-list-properties\", HMP command\n\"device_add T,help\", and command line option \"-device T,help\".\n\nLegacy properties are gone since commit a61383f7ab (qdev: Legacy\nproperties are now unused internally, drop, 2025-10-22).  This makes\nthe fix easy: delete the code that skips them.\n\nReproducer: -device nvme,help doesn\u0027t show legacy-cmb before the\npatch, and does after.\n\nFixes: f4eb32b590 (qmp: show QOM properties in device-list-properties, 2014-05-20)\nSigned-off-by: Markus Armbruster \u003carmbru@redhat.com\u003e\nMessage-ID: \u003c20260708140948.2622814-1-armbru@redhat.com\u003e\nReviewed-by: Daniel P. Berrangé \u003cberrange@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "48b38d2b7f733239cdf186f606f76f4a53293287",
      "old_mode": 33188,
      "old_path": "qom/qom-qmp-cmds.c",
      "new_id": "330895361d47a3289e68f5cd35591140523db201",
      "new_mode": 33188,
      "new_path": "qom/qom-qmp-cmds.c"
    }
  ]
}