)]}'
{
  "commit": "5a1a087baebcc4a996de66c558bac49419034ee0",
  "tree": "ad386b2556a0072a39ea88ad36c54369c36cf68d",
  "parents": [
    "515812ddbbb6a41298261688c8ccd0df8e900f17"
  ],
  "author": {
    "name": "David Lamparter",
    "email": "equinox@opensourcerouting.org",
    "time": "Thu Aug 11 17:02:50 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_af_set() on fresh circuit\n\nA newly-created circuit will be in enabled state but have neither IPv4\nnor IPv6 configured.  The logic in isis_circuit_af_set assumed that\n\"enabled\" is equivalent to \"ip || ipv6\".\n\nThis is the only place where this distinction is currently relevant, as\nthe CLI won\u0027t allow enabling an interface without enabling either IPv4\nor IPv6;  and it will also disable a circuit when both are deconfigured.\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": "b830794cb3ff84a905b1aba4b532456fbfe112c0",
      "old_mode": 33188,
      "old_path": "isisd/isis_circuit.c",
      "new_id": "4acd8f3b6b24552161e85a0ea5cec51878da9953",
      "new_mode": 33188,
      "new_path": "isisd/isis_circuit.c"
    }
  ]
}