)]}'
{
  "commit": "4cdda229da53bde30b2a22155ee7ceb025cebc49",
  "tree": "f6c8cd0c07dd21957bd70fc6f14dd4c8f151586d",
  "parents": [
    "48680a5f9d8ec2fcfa349ff2006a21b3b788b959"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Fri Jan 06 10:37:10 2023 -0500"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Thu Jan 26 14:31:33 2023 -0500"
  },
  "message": "gdb/testsuite/dap: write requests to gdb.log\n\nThis helps following what happens when reading gdb.log.  The downside is\nthat it becomes harder to tell what text is from GDB and what text is\ngoing to GDB, but I think that seeing responses without seeing requests\nis even more confusing.  At least, the lines are prefix with \u003e\u003e\u003e, so\nwhen you see this, you know that until the end of the line, it\u0027s\nsomething that was sent to GDB, and not GDB output.\n\nChange-Id: I1ba1acd8b16f4e64686c5ad268cc41082951c874\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a91b55336438f2f39aa9432d44b2c6aa7859bd55",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/dap-support.exp",
      "new_id": "94a0d27c8a8571b951f1c771f868c18e3db58d7c",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/dap-support.exp"
    }
  ]
}
