)]}'
{
  "commit": "65ca75e0d1e7e440bf0d2a6a031d4148024c9d12",
  "tree": "71826429ce3985bf3900be4a965de238ac668e82",
  "parents": [
    "a3b6ea56a0add7d0972a66d96e1fbcf5461eecdb"
  ],
  "author": {
    "name": "Paul Jakma",
    "email": "paul.jakma@sun.com",
    "time": "Thu May 04 08:08:15 2006 +0000"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul.jakma@sun.com",
    "time": "Thu May 04 08:08:15 2006 +0000"
  },
  "message": "[bgpd] Fix bug where FSM can stay hung forever in Idle/Clrng\n\n2006-05-04 Paul Jakma \u003cpaul.jakma@sun.com\u003e\n\n\t* bgp_route.c: (general) Fix logical bug in clearing, noted\n\t  by Chris Caputo in [quagga-users 6728] - clearing depended on\n\t  at least one route being added to workqueue, in order for\n\t  workqueue completion function to restart FSM. However, if no\n\t  routes are cleared, then the completion function never is\n\t  called, it needs to be called manually if the workqueue\n\t  didn\u0027t get scheduled.\n\t  Finally, clearing is per-peer-session, not per AFI/SAFI, so\n\t  the FSM synchronisation should be in bgp_clear_route_table.\n\t  (bgp_clear_route_table) Wrong place for FSM/clearing\n\t  synchronisation, move to..\n\t  (bgp_clear_route) FSM/clearing synchronisation should be\n\t  here.\n\t  If no routes were cleared, no workqueue scheduled, call\n\t  the completion func to ensure FSM kicks off again.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a0ba520c7a9413d6764b17acbb4092443b3a00d3",
      "old_mode": 33188,
      "old_path": "bgpd/ChangeLog",
      "new_id": "5599801e681d444251bcc9f58dee81df5c898109",
      "new_mode": 33188,
      "new_path": "bgpd/ChangeLog"
    },
    {
      "type": "modify",
      "old_id": "b49bea9880b6644a63ae1f8767b8c134e347a0c1",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_route.c",
      "new_id": "10c88697921aedbe5af6e545aba03a8c139e8144",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_route.c"
    }
  ]
}