)]}'
{
  "commit": "fb214471c88616d67ece3734128ef04ed4a8ed86",
  "tree": "04894d9d96861039b8b0cb1677d58c23e206acb3",
  "parents": [
    "605aa331d814b0977dd8435168dca5b2b7928996"
  ],
  "author": {
    "name": "Piotr Chytła",
    "email": "pch@packetconsulting.pl",
    "time": "Tue Dec 01 13:47:06 2015 -0500"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul.jakma@hpe.com",
    "time": "Tue Oct 04 13:07:49 2016 +0100"
  },
  "message": "zebra: add support for route tags\n\n[Forward ported by Cumulus]\n\nDocumentation\n-------------\nAll ipv4 and ipv6 static route commands now have a \"tag\" option\nwhich allows the user to set a tag between 1 and 65535.\n\nquagga(config)# ip route 1.1.1.1/32 10.1.1.1 tag ?\n  \u003c1-65535\u003e  Tag value\nquagga(config)# ip route 1.1.1.1/32 10.1.1.1 tag 40\nquagga(config)#\n\nquagga# show ip route 1.1.1.1/32\nRouting entry for 1.1.1.1/32\n Known via \"static\", distance 1, metric 0, tag 40, best\n * 10.1.1.1, via swp1\n\nquagga#\n\nThe route-map parser supports matching on tags and setting tags\n!\nroute-map MATCH_TAG_18 permit 10\n match tag 18\n!\n\n!\nroute-map SET_TAG_22 permit 10\n set tag 22\n!\n\nBGP and OSPF support:\n- matching on tags when redistribing routes from the RIB into BGP/OSPF.\n- setting tags when redistribing routes from the RIB into BGP/OSPF.\n\nBGP also supports setting a tag via a table-map, when installing BGP\nroutes into the RIB.\n\nSigned-off-by: Daniel Walton \u003cdwalton@cumulusnetworks.com\u003e\nSigned-off-by: Piotr Chytla \u003cpch@packetconsulting.pl\u003e\nSigned-off-by: Donald Sharp \u003csharpd@cumulusnetworks.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "08144cb8d78216fc82f4c8099a7c4c8edcd8c97a",
      "old_mode": 33188,
      "old_path": "zebra/zebra_vty.c",
      "new_id": "a14f68b925c8b8254818c1b2f39be96427ee944f",
      "new_mode": 33188,
      "new_path": "zebra/zebra_vty.c"
    }
  ]
}