)]}'
{
  "commit": "7798b6321cd0c6281b1a119ac894ff3749e88cc1",
  "tree": "2be0e1ed9af8a9fdf156d013287c154cb081965a",
  "parents": [
    "f92c57f8ba4f1e856934ec1736be3cad62be4785"
  ],
  "author": {
    "name": "Andrew Certain",
    "email": "certain@amazon.com",
    "time": "Tue Dec 04 13:33:24 2012 -0800"
  },
  "committer": {
    "name": "Scott Feldman",
    "email": "sfeldma@cumulusnetworks.com",
    "time": "Mon Jan 07 09:59:51 2013 -0800"
  },
  "message": "lib: Changes to VTY string-parsing macros to remove warnings\n\nThe VTY_GET_INTEGER_RANGE macro was being used also just to check the range\non a variable that wasn\u0027t used (for the \"no\" version of a VTY command), so I\nsplit the macro into two.  Also, since the variable is unsigned, if MIN is\nzero, you get a warning about comparing an unsigned number against 0, giving\nrise to slightly convoluted logic.  Note that the previous two patches were\nfound by the -Wtype-limits and -Wunused-variables warnings.  Without the\nchanges to these macros, these warnings are triggered erroneously, making it\nharder to find the real problems.\n\nSigned-off-by: Scott Feldman \u003csfeldma@cumulusnetworks.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e5158687d0fa99f68056aefaaf0148b90e466bb3",
      "old_mode": 33188,
      "old_path": "lib/vty.h",
      "new_id": "1798585ecadc6af14c9ac02d9fb001aa8180c85c",
      "new_mode": 33188,
      "new_path": "lib/vty.h"
    }
  ]
}
