)]}'
{
  "commit": "782c882077b5a63213b3d160535d5e8259f6df61",
  "tree": "31a9ed3f8d228f41080e684557b48939943ee6a8",
  "parents": [
    "8ccd74c29f5242f312c1e0561497558482c9be65"
  ],
  "author": {
    "name": "Donald Sharp",
    "email": "sharpd@cumulusnetworks.com",
    "time": "Mon Sep 14 13:29:37 2015 -0400"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul@quagga.net",
    "time": "Thu Sep 24 15:26:45 2015 +0100"
  },
  "message": "zebra: rib-\u003enexthop_num is double incremented\n\nWhile reading linux kernel netlink messages, rib-\u003enexthop_num is incremented\nin the read loop as well as the underlying nexthop_add() function call.  This\nnumber should only be incremented in one spot.  Removing the increment from\nthe read loop and allowing the underlying code to track this data as it is\nalready.\n\nSigned-off-by: Donald Sharp \u003csharpd@cumulusnetworks.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "33fbc0805ae1ab3fa4a91722d4f24dd747de4d5d",
      "old_mode": 33188,
      "old_path": "zebra/rt_netlink.c",
      "new_id": "cbcbe7c566186b3354c9cec0c1f3e713697ed580",
      "new_mode": 33188,
      "new_path": "zebra/rt_netlink.c"
    }
  ]
}