)]}'
{
  "commit": "2820a01eed1c616d490ddbfd17793c19597459d1",
  "tree": "6a0e418ca25166bd2edcc23a070b4c23d6f99a81",
  "parents": [
    "782fb0770080d0e2970fc63af8645e82543aa4d0"
  ],
  "author": {
    "name": "Timo Teräs",
    "email": "timo.teras@iki.fi",
    "time": "Wed Jun 24 15:27:21 2015 +0300"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul@quagga.net",
    "time": "Thu Sep 24 15:26:42 2015 +0100"
  },
  "message": "bgpd: Make bgp_info_cmp robust to paths that do not have su_remote info\n\nMy original su_remote \u003d\u003d NULL check is not correct. It seems that\n\n* bgp_route.c: (bgp_info_cmp) Some bgp_info is compared with su_remote\u003dNULL\n  and it\u0027s supposed to be perfectly legal.  E.g.  configured subnet announces\n  (\"network a.b.c.d/n\"). Ensure bgp_info_cmp is robust if such a path gets\n  as far as the neighbour address comparison step.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f40127195f076194ab01a3db2f610389f733897f",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_route.c",
      "new_id": "40012ac265ad46995f9b5423de22dcd0208724cd",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_route.c"
    }
  ]
}