)]}'
{
  "commit": "e0630cb4d61557f956318a088f68f1fc4d261ef3",
  "tree": "954964aed06b0247b59686d73e109218951df369",
  "parents": [
    "d265548ffb8da9ba3e1dd327efbff31c7cd15027"
  ],
  "author": {
    "name": "Dinesh G Dutt",
    "email": "ddutt@cumulusnetworks.com",
    "time": "Mon Jan 07 10:12:52 2013 -0800"
  },
  "committer": {
    "name": "Scott Feldman",
    "email": "sfeldma@cumulusnetworks.com",
    "time": "Mon Jan 07 10:12:52 2013 -0800"
  },
  "message": "ospfd: Remove dup MaxAge LSA flood\n\nStop additional, unnecessary flooding of MaxAge LSAs.\n\nWhen a MaxAge LSA is installed, if the LSA is prematurely aged or the LSA is\nnot self-originated, the LSA is flushed. This results in a the LSA being\nflooded a second time and in some cases flooded back to the receiver\n(unless the receiver is also the advertising router). A MaxAge\u0027d LSA has\nalready been flooded in ospf_flood() as part of the LSA receive processing\n(ospf_ls_upd). A self-originated LSA will be flooded from the originate/refresh\nroutine. Thus, in the install routine, a MaxAge\u0027d LSA only needs to be added\nto the MaxAge LSA list.\n\nSigned-off-by: Dinesh G Dutt \u003cddutt@cumulusnetworks.com\u003e\nSigned-off-by: Scott Feldman \u003csfeldma@cumulusnetworks.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4f7fb00aaca5bcbe0f9e7b6eb5e11feee8a1f461",
      "old_mode": 33188,
      "old_path": "ospfd/ospf_lsa.c",
      "new_id": "dfd1a61e2a3e84efef20a28ba3983b98bccc74cb",
      "new_mode": 33188,
      "new_path": "ospfd/ospf_lsa.c"
    }
  ]
}