)]}'
{
  "commit": "5e7cf3e91c8f8fb13f2f4d6a8639f6243c8ce003",
  "tree": "6e40199ee905d25c1b63d285d267706555332d6c",
  "parents": [
    "e372330056114785c4cb2e0afa699d95c9835eee"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Sat Jan 03 16:04:41 2026 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Sat Jan 03 16:04:41 2026 +0100"
  },
  "message": "[pre-commit] Move codespell-log back to commit-msg stage\n\nCommit 7acd390ffd9 (\"[pre-commit] Move codespell-log to post-commit\") moved\nthe codespell-log hook from the commit-msg to the post-commit stage.\n\nThis was deemed to make git rebase too slow [1], so move it back to the\ncommit-msg stage.  Don\u0027t do this using a full revert, to keep unrelated\nimprovements from that commit.\n\nSince we use codespell-log to produce warnings rather than errors, running the\nhook at the commit-msg stage requires us to ignore codespell exit status, and\nset verbose\u003dtrue.\n\n[1] https://sourceware.org/pipermail/gdb-patches/2025-December/223533.html\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e0c80428875260318b0a51c11e6b9b2ae19d79f4",
      "old_mode": 33188,
      "old_path": ".pre-commit-config.yaml",
      "new_id": "3bed91e50f69cf9ce062713e301ef34eb3621831",
      "new_mode": 33188,
      "new_path": ".pre-commit-config.yaml"
    },
    {
      "type": "modify",
      "old_id": "3873fd7a5a9fa89c0c36e0aa617ffe23bdeeca44",
      "old_mode": 33261,
      "old_path": "gdb/contrib/codespell-log.sh",
      "new_id": "992483d01650d120b2513b5a3120466e20c638b9",
      "new_mode": 33261,
      "new_path": "gdb/contrib/codespell-log.sh"
    }
  ]
}