)]}'
{
  "log": [
    {
      "commit": "6ae80e0d80531f602c3cb0e535c4e12bd2181b40",
      "tree": "2d62c703648a90b46d5a4dec680a126667246128",
      "parents": [
        "030674d7f9b2a25d4d337459ef32287de8f9879d"
      ],
      "author": {
        "name": "Donald Sharp",
        "email": "sharpd@cumulusnetworks.com",
        "time": "Thu Jun 18 18:14:20 2015 -0700"
      },
      "committer": {
        "name": "Paul Jakma",
        "email": "paul@quagga.net",
        "time": "Fri Aug 21 17:25:18 2015 +0100"
      },
      "message": "pimd: Add ability to set DR Priority for an interface\n\nFrom RFC 4601, Section 4.3.1:\n\nThe DR_Priority Option allows a network administrator to give\npreference to a particular router in the DR election process by\ngiving it a numerically larger DR Priority.  The DR_Priority Option\nSHOULD be included in every Hello message, even if no DR Priority is\nexplicitly configured on that interface.  This is necessary because\npriority-based DR election is only enabled when all neighbors on an\ninterface advertise that they are capable of using the DR_Priority\nOption.  The default priority is 1.\n\nThis modification allows the setting of the DR Priority on a per\ninterface basis.\n\nSigned-off-by: Donald Sharp \u003csharpd@cumulusnetworks.com\u003e\n"
    },
    {
      "commit": "871dbcfede60a8d2d286728bcbd88f27c2035b87",
      "tree": "f3188f3ab1c4856febf70647a32f6d854668aa50",
      "parents": [
        "b162ab753e70328cb6815e58b4bc5b03e9dd4f42"
      ],
      "author": {
        "name": "Everton Marques",
        "email": "everton.marques@gmail.com",
        "time": "Tue Aug 11 15:43:05 2009 -0300"
      },
      "committer": {
        "name": "David Lamparter",
        "email": "equinox@opensourcerouting.org",
        "time": "Wed Feb 04 06:07:49 2015 +0100"
      },
      "message": "[pim] Initial pim 0.155\n"
    }
  ]
}