)]}'
{
  "commit": "b172d94b62b8a27c9d79cf70e565e31b21439c98",
  "tree": "5985e8b99af63ddfd875f0b5b01fc0e35b76396a",
  "parents": [
    "7934cb137a779ca41123a673243027b1e6dd99e9"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Fri Apr 14 14:45:38 2023 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Sat Jul 20 17:29:39 2024 +0100"
  },
  "message": "gdb: remove breakpoint_re_set_one\n\nDuring a later patch I wanted to reset a single breakpoint, so I\ncalled breakpoint_re_set_one.  However, this is not the right thing to\ndo.  If we look at breakpoint_re_set then we see that there\u0027s a whole\nbunch of state that needs to be preserved prior to calling\nbreakpoint_re_set_one, and after calling breakpoint_re_set_one we\nstill need to call update_global_location_list.\n\nI could just update the comment on breakpoint_re_set_one to make it\nclearer how the function should be used -- or more likely to warn that\nthe function should only be used as a helper from breakpoint_re_set.\n\nHowever, breakpoint_re_set_one is only 3 lines long.  So I figure it\nmight actually be easier to just fold breakpoint_re_set_one into\nbreakpoint_re_set, then there\u0027s no risk of accidentally calling\nbreakpoint_re_set_one when we shouldn\u0027t.\n\nThere should be no user visible changes after this commit.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a9bb45685de96547e926d21a19cbd69a0e196e42",
      "old_mode": 33188,
      "old_path": "gdb/breakpoint.c",
      "new_id": "ad968c4742feb420fa3868b52261a47aad9d3da5",
      "new_mode": 33188,
      "new_path": "gdb/breakpoint.c"
    }
  ]
}