)]}'
{
  "commit": "2644874d9d3e6c16299a01acddf66cd99fd43414",
  "tree": "bd2e86186a48a22286c6e919758d7edf366bda9a",
  "parents": [
    "3d125940f6223efe62e35b795f57e7e717b4528e"
  ],
  "author": {
    "name": "Brian Harring",
    "email": "brian.harring@intel.com",
    "time": "Thu Apr 28 05:04:41 2011 -0700"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Thu May 24 09:07:24 2012 -0700"
  },
  "message": "ManifestXml: add include support\n\nHaving the ability to include other manifests is a very practical feature\nto ease the managment of manifest. It allows to divide a manifest into separate\nfiles, and create different environment depending  on what we want to release\n\nYou can have unlimited recursion of include, the manifest configs will simply be concatenated\nas if it was in a single file.\n\ncommand \"repo manifest\" will create a single manifest, and not recreate the manifest hierarchy\n\nfor example:\nOur developement manifest will look like:\n\n\u003c?xml version\u003d\u00271.0\u0027 encoding\u003d\u0027UTF-8\u0027?\u003e\n\u003cmanifest\u003e\n  \u003cdefault revision\u003d\"platform/android/main\" remote\u003d\"intel\"/\u003e\n  \u003cinclude name\u003d\"server.xml\"/\u003e \u003c!-- The Server configuration --\u003e\n  \u003cinclude name\u003d\"aosp.xml\" /\u003e  \u003c!-- All the AOSP projects --\u003e\n  \u003cinclude name\u003d\"bsp.xml\" /\u003e   \u003c!-- The BSP projects that we release in source form --\u003e\n  \u003cinclude name\u003d\"bsp-priv.xml\" /\u003e \u003c!-- The source of the BSP projects we release in binary form --\u003e\n\u003c/manifest\u003e\n\nOur release manifest will look like:\n\n\u003c?xml version\u003d\u00271.0\u0027 encoding\u003d\u0027UTF-8\u0027?\u003e\n\u003cmanifest\u003e\n  \u003cdefault revision\u003d\"platform/android/release-ext\" remote\u003d\"intel\"/\u003e\n  \u003cinclude name\u003d\"server.xml\"/\u003e \u003c!-- The Server configuration --\u003e\n  \u003cinclude name\u003d\"aosp.xml\" /\u003e  \u003c!-- All the AOSP projects --\u003e\n  \u003cinclude name\u003d\"bsp.xml\" /\u003e   \u003c!-- The BSP projects that we release in source form --\u003e\n  \u003cinclude name\u003d\"bsp-ext.xml\" /\u003e \u003c!-- The PREBUILT version of the BSP projects we release in binary form --\u003e\n\u003c/manifest\u003e\n\nAnd it is also easy to create and maintain feature branch with a manifest that looks like:\n\n\u003c?xml version\u003d\u00271.0\u0027 encoding\u003d\u0027UTF-8\u0027?\u003e\n\u003cmanifest\u003e\n  \u003cdefault revision\u003d\"feature_branch_foobar\" remote\u003d\"intel\"/\u003e\n  \u003cinclude name\u003d\"server.xml\"/\u003e \u003c!-- The Server configuration --\u003e\n  \u003cinclude name\u003d\"aosp.xml\" /\u003e  \u003c!-- All the AOSP projects --\u003e\n  \u003cinclude name\u003d\"bsp.xml\" /\u003e   \u003c!-- The BSP projects that we release in source form --\u003e\n  \u003cinclude name\u003d\"bsp-priv.xml\" /\u003e \u003c!-- The source of the BSP projects we release in binary form --\u003e\n\u003c/manifest\u003e\n\nSigned-off-by: Brian Harring \u003cbrian.harring@intel.com\u003e\nSigned-off-by: Pierre Tardy \u003cpierre.tardy@intel.com\u003e\nChange-Id: I833a30d303039e485888768e6b81561b7665e89d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "537896510a3b8f197df6a0135a23d24256953b9b",
      "old_mode": 33188,
      "old_path": "docs/manifest-format.txt",
      "new_id": "9f4585b8af674cf685e5603bfbe8e1f46f8ae326",
      "new_mode": 33188,
      "new_path": "docs/manifest-format.txt"
    },
    {
      "type": "modify",
      "old_id": "ca65e33fac287af6386bd8a6f558429d2983ae76",
      "old_mode": 33188,
      "old_path": "manifest_xml.py",
      "new_id": "2927fd1c00948992096b1351d10a0099b3a195e9",
      "new_mode": 33188,
      "new_path": "manifest_xml.py"
    }
  ]
}