)]}'
{
  "commit": "515812ddbbb6a41298261688c8ccd0df8e900f17",
  "tree": "520c4a03130356863365f19f9c19f293e6fdd3d1",
  "parents": [
    "f263413f762058d887aa7b2b6c502bd84af3c923"
  ],
  "author": {
    "name": "David Lamparter",
    "email": "equinox@opensourcerouting.org",
    "time": "Thu Aug 11 16:59:08 2016 +0200"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul.jakma@hpe.com",
    "time": "Tue Oct 04 13:07:55 2016 +0100"
  },
  "message": "isisd: fix isis_circuit_create()\n\nBetween the awkwardly managed CSM and the tacked-on IPv6 support, the\nsimplified logic to setup a circuit wasn\u0027t quite right.\n\nNote that the API essentially allows creating a circuit without enabling\neither IPv4 or IPv6.  This wasn\u0027t possible before and probably breaks\nisisd in \u0027interesting\u0027 ways.  The CLI won\u0027t do this, so it\u0027s only an\nissue when adding on other configuration mechanisms.\n\nReported-by: Martin Winter \u003cmwinter@opensourcerouting.org\u003e\nSigned-off-by: David Lamparter \u003cequinox@opensourcerouting.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "aa30fcdb748d7d031a714e73376c17fd01046e50",
      "old_mode": 33188,
      "old_path": "isisd/isis_circuit.c",
      "new_id": "b830794cb3ff84a905b1aba4b532456fbfe112c0",
      "new_mode": 33188,
      "new_path": "isisd/isis_circuit.c"
    },
    {
      "type": "modify",
      "old_id": "3f218561cc46744640140ec148a289a13fbdaa36",
      "old_mode": 33188,
      "old_path": "isisd/isis_vty.c",
      "new_id": "3ce06b83dadb7bb46cdd2d8beb3a9bd00fdff197",
      "new_mode": 33188,
      "new_path": "isisd/isis_vty.c"
    }
  ]
}