)]}'
{
  "commit": "f588bb034d5d3a0417f45965f1aba4d4cf8a2893",
  "tree": "b2f85b93db0bb7eb745016c6dc4d66089838a283",
  "parents": [
    "05f132d74d173854df79bc5541699c3db144e42a"
  ],
  "author": {
    "name": "Andy Fleming",
    "email": "afleming@freescale.com",
    "time": "Tue Apr 24 19:33:51 2012 +0000"
  },
  "committer": {
    "name": "Wolfgang Denk",
    "email": "wd@denx.de",
    "time": "Mon Apr 30 16:52:19 2012 +0200"
  },
  "message": "Allow for parallel builds and saved output\n\nThe MAKEALL script cleverly runs make with the appropriate options\nto use all of the cores on the system, but your average U-Boot build\ncan\u0027t make much use of more than a few cores.  If you happen to have\na many-core server, your builds will leave most of the system idle.\n\nIn order to make full use of such a system, we need to build multiple\ntargets in parallel, and this requires directing make output into\nmultiple directories. We add a BUILD_NBUILDS variable, which allows\nusers to specify how many builds to run in parallel.\nWhen BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for\neach build to be ${BUILD_DIR}/${target}. Also, we make \"./build\" the\ndefault BUILD_DIR when BUILD_NBUILDS is greater than 1.\n\nMAKEALL now tracks which builds are still running, and when one\nfinishes, it starts a new build.\n\nOnce each build finishes, we run \"make tidy\" on its directory, to reduce\nthe footprint.\n\nAs a result, we are left with a build directory with all of the built\ntargets still there for use, which means anyone who wanted to use\nMAKEALL as part of a test harness can now do so.\n\nSigned-off-by: Andy Fleming \u003cafleming@freescale.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e5da6f18599452f4ec68bff8190bf789dc402a34",
      "old_mode": 33261,
      "old_path": "MAKEALL",
      "new_id": "e6c801cbb88457ec58de8e8f60d20ab392966fe4",
      "new_mode": 33261,
      "new_path": "MAKEALL"
    }
  ]
}