)]}'
{
  "commit": "6ee06fa9ed91412cb745668d462031cdbe2642e0",
  "tree": "107e951abc716c2ca15fbcc62bdb0858b35036e8",
  "parents": [
    "a83a1e9c2f035d3152451dcfc97ab13b4ac427b9"
  ],
  "author": {
    "name": "Pradosh Mohapatra",
    "email": "pmohapat@cumulusnetworks.com",
    "time": "Sun Jan 12 18:30:13 2014 +0000"
  },
  "committer": {
    "name": "Vincent JARDIN",
    "email": "vincent.jardin@6wind.com",
    "time": "Mon Feb 10 09:37:30 2014 +0100"
  },
  "message": "bgpd: bgpd-set-v4-nexthop-for-v6-peering.patch\n\nBGP: While advertising v4 prefixes over a v6 session, set the correct v4 nexthop.\n\nISSUE:\n\nFor an IPv6 peer, BGPd sets the local router-id as the next-hop\u0027s v4 address.\nThis is incorrect as the router-id may not be a valid next-hop to be included\nin UPDATEs that contain v4 prefixes.\n\nPATCH:\n\nSet the v4 address in the next-hop field based on the interface that the\npeering is on (directly connected interface or loopback).\n\nSigned-off-by: Pradosh Mohapatra \u003cpmohapat at cumulusnetworks.com\u003e\nReviewed-by: Scott Feldman \u003csfeldma at cumulusnetworks.com\u003e\nAcked-by: Feng Lu \u003clu.feng@6wind.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "604438304375e54ec0a92d0009bfa23a1dea915e",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_zebra.c",
      "new_id": "26b97c2c482d27bd9351727c118d76583ecd6213",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_zebra.c"
    },
    {
      "type": "modify",
      "old_id": "7f0d36070b181f32de527c12b8134c375c16fa62",
      "old_mode": 33188,
      "old_path": "lib/prefix.h",
      "new_id": "8c8992e8cd8fa9de3cfdd21d920db1e21944fec4",
      "new_mode": 33188,
      "new_path": "lib/prefix.h"
    }
  ]
}