)]}'
{
  "commit": "3b847ef4e81c6f1a5d4994680d530045765fd053",
  "tree": "04fcd0f852e384ba862d815de4aef88b6a4505e8",
  "parents": [
    "7f39242bf44c85bb651506214666b3ebdd78b928"
  ],
  "author": {
    "name": "Paul Jakma",
    "email": "paul.jakma@hpe.com",
    "time": "Fri Apr 22 12:48:49 2016 +0100"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul.jakma@hpe.com",
    "time": "Tue Sep 13 10:36:43 2016 +0100"
  },
  "message": "bgpd: Squash spurious \"unknown afi\" log messages\n\n* bgp_packet.c: (bgp_update_receive) doesn\u0027t differentiate between NLRIs that\n  are 0 AFI/SAFI cause they weren\u0027t set, and those because a peer sent a\n  bogus AFI/SAFI, before sending sending what may be a misleading, spurious\n  log message.  Check the .nlri pointer is set and avoid this.\n\nIncorporating a suggestion from: G. Paul Ziemba \u003cunp@ziemba.us\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "740b0f1ce6038fbfe13ab5aa5498c6bc25d24473",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_packet.c",
      "new_id": "9743d064efa9f35acbf332f10c610ae4cd8bec06",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_packet.c"
    }
  ]
}