)]}'
{
  "commit": "0eab18f308d29bb54aa4667013ae505d73a72194",
  "tree": "1809453791b023fc10261ebe6233721ddbbb3064",
  "parents": [
    "8b471213b360b6b8eda2c2eba2b69ddc3c1366aa"
  ],
  "author": {
    "name": "Guy1524",
    "email": "35645466+Guy1524@users.noreply.github.com",
    "time": "Mon Aug 03 17:07:47 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Aug 03 16:07:47 2026 +0100"
  },
  "message": "Finalize MESA_map_buffer_client_pointer (#680)\n\n* MESA_map_buffer_client_pointer: add CLIENT_POINTER_RELEASE_ALL_MESA.\n\nAs discussed in PR (#678), introduce a flag to specifiy whether all possibly client pointer ranges\nshould be released, or just the one the driver isn\u0027t holding onto anymore, as releasing everything\nis slow and should be reserved for OOM situations.\n\nThis changes the ABI, as PR (#678) was merged before it was ready, and we don\u0027t yet have any consumers.\n\n* MESA_map_buffer_client_pointer: Require CLIENT_POINTER-enabled data stores.\n\nEnables the driver to pool resources with shared client range space into one BO.\nOtherwise implementations may have to either reshuffle memory at map-time, or support\nconcurrent mappings for the same memory.\n\n* MESA_map_buffer_client_pointer: Specify shareable state.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7c62cc314cefc8717d7765322c782c7c5a5eaff3",
      "old_mode": 33188,
      "old_path": "extensions/MESA/MESA_map_buffer_client_pointer.txt",
      "new_id": "b92f61ea3e19553d83c56fce3d483766a8e699f0",
      "new_mode": 33188,
      "new_path": "extensions/MESA/MESA_map_buffer_client_pointer.txt"
    },
    {
      "type": "modify",
      "old_id": "902d7aabcd5e6d6fdb348b20f1a1b9733dac5fbb",
      "old_mode": 33188,
      "old_path": "xml/gl.xml",
      "new_id": "7492d15565b79cf3844e3402858582f649677fec",
      "new_mode": 33188,
      "new_path": "xml/gl.xml"
    }
  ]
}