)]}'
{
  "commit": "bfdb52f83ca6ca3a0eb43ef2bd0f4f8193a06472",
  "tree": "d272d3d9dca9e3864d38eaf4e7f0232a4e937b40",
  "parents": [
    "f93c6e0a2ed1ad4f0a9bb8f38e859f3312c25282"
  ],
  "author": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Tue Apr 19 11:21:35 2022 -0600"
  },
  "committer": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Tue Apr 26 12:54:05 2022 -0600"
  },
  "message": "Handle encoding failures in Windows thread names\n\nInternally at AdaCore, we noticed that the new Windows thread name\ncode could fail.  First, it might return a zero-length string, but in\ngdb conventions it should return nullptr instead.  Second, an encoding\nfailure could wind up showing replacement characters to the user; this\nis confusing and not useful; it\u0027s better to recognize such errors and\nsimply discard the name.  This patch makes both of these changes.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bd1b94591456884476cb382236eb7617c13221f4",
      "old_mode": 33188,
      "old_path": "gdb/nat/windows-nat.c",
      "new_id": "c8db19439f3dbae4dec9da5f0d20ba661a48fa9c",
      "new_mode": 33188,
      "new_path": "gdb/nat/windows-nat.c"
    }
  ]
}