)]}'
{
  "commit": "149210656045c363d8f59b97ad9251b0c06a15df",
  "tree": "e107766b6b3ae49d7e8a7190cb3aa1e382a43f87",
  "parents": [
    "1c6db0d2da34044ddfb42665fda8a3387ecc451d"
  ],
  "author": {
    "name": "Olivier Dugeon",
    "email": "olivier.dugeon@orange.com",
    "time": "Mon Nov 03 14:59:06 2014 +0100"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul@quagga.net",
    "time": "Tue Jan 27 19:53:24 2015 +0000"
  },
  "message": "ospfd: Fix initial Opaque LSA DB  synchronisation\n\nospfd has issues resynchronising its Opaque LSA DB with neighbours after restart\nor interface events. The problem comes from opaque_lsa.c code that blocks\nsubsequent opaque LSA flooding until the neighbour router acknowledge that, and\nremoves the old opaque LSA from its LSDB. The bug comes from the fact that the\nlock is never release, thus avoiding subsequent opaque LSA flooding.\n\nMore detail about the bugs and its solution is describeid in file\ndoc/te-link-params.md\n\nSigned-off-by: Olivier Dugeon \u003colivier.dugeon@orange.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "744952c96eef2cc9c5fee0c41f82b990da1d8b14",
      "old_mode": 33188,
      "old_path": "ospfd/ospf_opaque.c",
      "new_id": "ecb28ffe3d8efd4703f20ee20848c6748904d0b0",
      "new_mode": 33188,
      "new_path": "ospfd/ospf_opaque.c"
    }
  ]
}