)]}'
{
  "commit": "2864e855932540c3ec6c9bf41ee3fe027d85f642",
  "tree": "740e00df6e2332955c05232295a7ef9e7e513971",
  "parents": [
    "c1db9880936d752d8c2f56ab1aae01dd247de5d9",
    "f402c7941f19fa518e44b24bf31f3b6c3542c115"
  ],
  "author": {
    "name": "Johannes Sixt",
    "email": "j6t@kdbg.org",
    "time": "Sun Jul 07 14:00:23 2024 +0200"
  },
  "committer": {
    "name": "Johannes Sixt",
    "email": "j6t@kdbg.org",
    "time": "Sun Jul 07 14:14:59 2024 +0200"
  },
  "message": "Merge branch \u0027os/catch-rename\u0027\n\nThe problem can be reproduced on Linux with this sequence:\n\n1. Run git gui from a terminal.\n2. Edit the commit message and wait for at least 2 seconds.\n3. Terminate the instance from the terminal, for example with Ctrl-C,\n   to simulate crash. This leaves the file .git/GITGUI_BCK behind.\n4. Start two instances of git gui \u0026.\n\nAt this point the first instance can be closed (it renames\n.git/GITGUI_BCK to .git/GITGUI_MSG), but the seconds brings an error\nmessage about the absent file and cannot be closed thereafter and must\nbe killed from the command line.\n\nThe renaming that happens by the first instance is the correct action\nand need not be repeated by the second instance. It is the correct\naction to ignore the failed renaming.\n\nOn the other hand, the second instance could just edit the commit\nmessage again, wait 2 seconds to write GITGUI_BCK, and then can be\nclosed without failing. At this point, since the user has edited the\nmessage, it is again correct to preserve the edited version in\nGITGUI_MSG.\n\n* os/catch-rename:\n  git-gui: fix inability to quit after closing another instance\n",
  "tree_diff": []
}