)]}'
{
  "commit": "0ebf1bdeeda1612dbe8e092dca765527a741e462",
  "tree": "d5d25653b93e29653bd7c6b41a01ffb4ec1b65c0",
  "parents": [
    "eb244227d83c81fa17ec2f5ddc933945b14217fd"
  ],
  "author": {
    "name": "Nick Alcock",
    "email": "nick.alcock@oracle.com",
    "time": "Tue Apr 02 13:48:13 2024 +0100"
  },
  "committer": {
    "name": "Nick Alcock",
    "email": "nick.alcock@oracle.com",
    "time": "Fri Apr 19 16:14:47 2024 +0100"
  },
  "message": "libctf: improve handling of type dumping errors\n\nWhen dumping a type fails with an error, we want to emit a warning noting\nthis: a warning because it\u0027s not fatal and we can continue.  But warnings\ndon\u0027t automatically print out the ctf_errno (because not all cases causing\nwarnings set the errno at all), so we must do it at warning-emission time or\nlose track of what\u0027s gone wrong.\n\nlibctf/\n\n\t* ctf-dump.c (ctf_dump_format_type): Dump the underlying error on\n\ttype dump failure.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2213d09dc29261e26fbff21d09ca18bb10de5684",
      "old_mode": 33188,
      "old_path": "libctf/ctf-dump.c",
      "new_id": "80a3b2652971b75df096a25ecfacfceb44f0e9b2",
      "new_mode": 33188,
      "new_path": "libctf/ctf-dump.c"
    }
  ]
}