)]}'
{
  "commit": "afc9cf97363c0b7ec6c253731a75ac83e70ea190",
  "tree": "929cddfa8cda9136780bccd28ce365365841b3cc",
  "parents": [
    "fc2cee2bed4ebf664ba0afa1678027365f3923f7"
  ],
  "author": {
    "name": "Vipin Kumar",
    "email": "vipin@cumulusnetworks.com",
    "time": "Tue May 19 18:03:50 2015 -0700"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul.jakma@hpe.com",
    "time": "Tue Oct 04 13:07:51 2016 +0100"
  },
  "message": "osfd: Make OSPF compliant to the last sentence of this section in RFC 2328\n\n9.5 Sending Hello packets\n\nHello packets are sent out each functioning router interface.\nThey are used to discover and maintain neighbor\nrelationships.[6] On broadcast and NBMA networks, Hello Packets\nare also used to elect the Designated Router and Backup\nDesignated Router.\nThe format of an Hello packet is detailed in Section A.3.2.  The\nHello Packet contains the router\u0027s Router Priority (used in\nchoosing the Designated Router), and the interval between Hello\nPackets sent out the interface (HelloInterval).  The Hello\nPacket also indicates how often a neighbor must be heard from to\nremain active (RouterDeadInterval).  Both HelloInterval and\nRouterDeadInterval must be the same for all routers attached to\na common network.  The Hello packet also contains the IP address\nmask of the attached network (Network Mask).  On unnumbered\npoint-to-point networks and on virtual links this field should\nbe set to 0.0.0.0.\n\nSigned-off-by: Vipin Kumar \u003cvipin@cumulusnetworks.com\u003e\nReviewed-by: Vivek Venkatraman \u003cvivek@cumulusnetworks.com\u003e\nReviewed-by: Dinesh G Dutt \u003cddutt@cumulusnetworks.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f14182235eca842d63c550f8da46be3c8598f042",
      "old_mode": 33188,
      "old_path": "ospfd/ospf_packet.c",
      "new_id": "facba89509de0998ed4a04801a7d9e37ca76bfaa",
      "new_mode": 33188,
      "new_path": "ospfd/ospf_packet.c"
    }
  ]
}