)]}'
{
  "commit": "e5a9a4076f1fb9fb9ce53c2aec32422073bbc66a",
  "tree": "6ca5540adfae4503242ece100b3cd9eed65fb26f",
  "parents": [
    "5b6da28352f4ae64d78a12e608133c1b876b992c"
  ],
  "author": {
    "name": "Rob Herring",
    "email": "rob.herring@calxeda.com",
    "time": "Fri Oct 18 13:04:42 2013 -0500"
  },
  "committer": {
    "name": "Tom Rini",
    "email": "trini@ti.com",
    "time": "Mon Nov 04 11:24:22 2013 -0500"
  },
  "message": "pxe: fix handling of absolute paths\n\npxelinux and syslinux differ in their handling of absolute paths in menu\nfiles. A pxelinux path is aways prepended with the bootfile path while\nsyslinux allows for absolute paths. u-boot was always treating a leading\n/ as an absolute path breaking some pxelinux setups. Fix this by adding\na flag to distinguish pxelinux vs. syslinux behavior.\n\nReported-by: Ian Campbell \u003cIan.Campbell@citrix.com\u003e\nSigned-off-by: Rob Herring \u003crob.herring@calxeda.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "79d3a061f537f6c1fe5a527b0d13bde3d7a2834e",
      "old_mode": 33188,
      "old_path": "common/cmd_pxe.c",
      "new_id": "db6b156985b735c2287192c66b695f2ccbae4af2",
      "new_mode": 33188,
      "new_path": "common/cmd_pxe.c"
    }
  ]
}
