)]}'
{
  "commit": "2a7d1e5ebbab35a6f3ff164653dfd0ba0e4448c0",
  "tree": "7f688e5fa951c1be0199c19762e56fe0398d30e3",
  "parents": [
    "3741934fdb04cde6661335e160249f9a83e498a7"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Mar 17 19:25:18 2023 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Mar 17 19:25:18 2023 +0100"
  },
  "message": "[gdb/testsuite] Handle REMOTE_HOST_USERNAME in local-remote-host\n\nHandle REMOTE_HOST_USERNAME in local-remote-host, similar to how that\u0027s done for\nREMOTE_TARGET_USERNAME in remote-gdbserver-on-localhost.\n\nThis helps to keep the home dir clean.\n\nSince the setup makes $build/gdb/testsuite on build unreadable for the remote\nhost, we run into permission problems for GDB and the data-directory, so fix\nthis (as was done for gdbserver in gdbserver-base.exp) using file normalize.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e208504788281ffd33a4fe4f34c11b4d82a2ea23",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/boards/local-remote-host.exp",
      "new_id": "f265208ddd992d31fb01acaf7a9fc88de09c407b",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/boards/local-remote-host.exp"
    },
    {
      "type": "modify",
      "old_id": "7ceb702b0bf3afa3ec64953c38c1c6d653e6dc19",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "8f3bbd986f5c87de4662f339f5214ae74c64c957",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}