)]}'
{
  "commit": "a031c4dd72514232296e9a570c3d701f5f33ad63",
  "tree": "7c155a444fa26bc8c30426ae5905c9f6f6c2fab3",
  "parents": [
    "73de55a53c78d572f63d45115681567a4c0cef65"
  ],
  "author": {
    "name": "Donald Sharp",
    "email": "sharpd@cumulusnetworks.com",
    "time": "Thu Jul 02 13:22:49 2015 -0400"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul@quagga.net",
    "time": "Fri Aug 21 17:25:18 2015 +0100"
  },
  "message": "pimd: Ensure new generation_id is different from previous\n\nThe RFC states that an interfaces generation_id must be changed\nif it experiences an if down.  From 4.3.1:\n\nThe GenID option contains a randomly generated\n32-bit value that is regenerated each time PIM forwarding is started\nor restarted on the interface, including when the router itself\nrestarts.\n\nSince we are only grabbing a new generation_id without comparing\nit to the previous generation_id, it is possible that random\ncan generate the exact same number.\n\nSigned-off-by: Donald Sharp \u003csharpd@cumulusnetworks.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7dcb501997b8df59baf9decad298b93b484fc920",
      "old_mode": 33188,
      "old_path": "pimd/pim_pim.c",
      "new_id": "41c26a8883b6af32e706bf19aab0f74f991d8d69",
      "new_mode": 33188,
      "new_path": "pimd/pim_pim.c"
    }
  ]
}
