)]}'
{
  "log": [
    {
      "commit": "0b4cb325c6f412ac5ab33573b4f5e50b4945c924",
      "tree": "c09284588db5cd85958c9270bba63b41b67a15d4",
      "parents": [
        "e9becc079c647f6c9477eed83c0aecb2f591fdf4"
      ],
      "author": {
        "name": "Xiaohui Chen",
        "email": "xiaohuic@google.com",
        "time": "Wed Jan 27 14:33:51 2016 -0800"
      },
      "committer": {
        "name": "Xiaohui Chen",
        "email": "xiaohuic@google.com",
        "time": "Thu Jan 28 10:20:03 2016 -0800"
      },
      "message": "Add option to rebase onto project\u0027s manifest version\n\nSome teams have a continuous build server that would mark certain\nmanifest green and safe to sync to.  Then team members could repo\nsync to that particular manifest file and make sure they always\nsync to a green build.  But if she/he has some local changes and\nwants to rebase, currently it would be a manual process to find the\ncorrect version to rebase onto.  This patch helps with that use\ncase by automating the process to rebase onto the currently synced\nmanifest version.\n\nChange-Id: I847c9eb6addf7f84fd3f5594fbf8c0bcc103f9a5\n"
    },
    {
      "commit": "8d20116038ff78b22069dd4e993b5819775f03d1",
      "tree": "4c7ec381f2452d3ae4ed5332230a8d7a61e6ec2b",
      "parents": [
        "b25ea555c39cd500740acb74fa9f1dab71588266"
      ],
      "author": {
        "name": "David James",
        "email": "davidjames@google.com",
        "time": "Fri Oct 11 17:03:19 2013 -0700"
      },
      "committer": {
        "name": "David James",
        "email": "davidjames@google.com",
        "time": "Mon Oct 14 15:34:32 2013 -0700"
      },
      "message": "repo: Support multiple branches for the same project.\n\nIt is often useful to be able to include the same project more than\nonce, but with different branches and placed in different paths in the\nworkspace. Add this feature.\n\nThis CL adds the concept of an object directory. The object directory\nstores objects that can be shared amongst several working trees. For\nnewly synced repositories, we set up the git repo now to share its\nobjects with an object repo.\n\nEach worktree for a given repo shares objects, but has an independent\nset of references and branches. This ensures that repo only has to\nupdate the objects once; however the references for each worktree are\nupdated separately. Storing the references separately is needed to\nensure that commits to a branch on one worktree will not change the\nHEAD commits of the others.\n\nOne nice side effect of sharing objects between different worktrees is\nthat you can easily cherry-pick changes between the two worktrees\nwithout needing to fetch them.\n\nBug: Issue 141\nChange-Id: I5e2f4e1a7abb56f9d3f310fa6fd0c17019330ecd\n"
    },
    {
      "commit": "2f9e7e40c44acae37d0c263c212956ef6038c35b",
      "tree": "b5bffccb2c4f6a502a350bef3e40183f56ca8bc9",
      "parents": [
        "45d21685b93f80b67239849b2d2cfe6b217e335a"
      ],
      "author": {
        "name": "David Pursehouse",
        "email": "david.pursehouse@sonymobile.com",
        "time": "Tue Mar 05 17:26:46 2013 +0900"
      },
      "committer": {
        "name": "David Pursehouse",
        "email": "david.pursehouse@sonymobile.com",
        "time": "Tue Mar 05 17:30:59 2013 +0900"
      },
      "message": "Fix: Missing spaces in printed messages\n\nSeveral messages are printed with the `print` method and the message\nis split across two lines, i.e.:\n\n print(\u0027This is a message split\u0027\n       \u0027across two source code lines\u0027)\n\nWhich causes the message to be printed as:\n\n This is a message splitacross two source code lines\n\nAdd a space at the end of the first line before the line break:\n\n print(\u0027This is a message split \u0027\n       \u0027across two source code lines\u0027\n\nAlso correct a minor spelling mistake.\n\nChange-Id: Ib98d93fcfb98d78f48025fcc428b6661380cff79\n"
    },
    {
      "commit": "cecd1d864fc3cf02cf50d367111e0d0e173c5dc6",
      "tree": "b4f660400560dce21cd7a00ffe5a5d74b54bcb81",
      "parents": [
        "fc241240d828d7e8302dc0876608a9d27ae1cbc7"
      ],
      "author": {
        "name": "Sarah Owens",
        "email": "sarato@inkylabs.com",
        "time": "Thu Nov 01 22:59:27 2012 -0700"
      },
      "committer": {
        "name": "Sarah Owens",
        "email": "sarato@inkylabs.com",
        "time": "Tue Nov 13 17:33:56 2012 -0800"
      },
      "message": "Change print statements to work in python3\n\nThis is part of a series of changes to introduce Python3 support.\n\nChange-Id: I373be5de7141aa127d7debdbce1df39148dbec32\n"
    },
    {
      "commit": "8a68ff96057ec58e524a3e41a2d8dca7b5d016bc",
      "tree": "22f6971e8d3c4a90d11d3704602d073a852328b4",
      "parents": [
        "e3b1c45aebed329cbc9ad172b1d8e812cf208117"
      ],
      "author": {
        "name": "David Pursehouse",
        "email": "david.pursehouse@sonymobile.com",
        "time": "Mon Sep 24 12:15:13 2012 +0900"
      },
      "committer": {
        "name": "Gustaf Lundh",
        "email": "gustaf.lundh@sonymobile.com",
        "time": "Tue Oct 09 12:45:30 2012 +0200"
      },
      "message": "Coding style cleanup\n\nFix the following issues reported by pylint:\n\nC0321: More than one statement on a single line\nW0622: Redefining built-in \u0027name\u0027\nW0612: Unused variable \u0027name\u0027\nW0613: Unused argument \u0027name\u0027\nW0102: Dangerous default value \u0027value\u0027 as argument\nW0105: String statement has no effect\n\nAlso fixed a few cases of inconsistent indentation.\n\nChange-Id: Ie0db839e7c57d576cff12d8c055fe87030d00744\n"
    },
    {
      "commit": "e15c65abc25cd1d5d77ec6815a3c011b9f57ddac",
      "tree": "43bd95e2e83abcd88c5d05b6a65393877c51028b",
      "parents": [
        "daa851f6cd9edb3851a3884fd2864f0f3dc583b2"
      ],
      "author": {
        "name": "David Pursehouse",
        "email": "david.pursehouse@sonymobile.com",
        "time": "Wed Aug 22 10:46:11 2012 +0900"
      },
      "committer": {
        "name": "Gustaf Lundh",
        "email": "gustaf.lundh@sonymobile.com",
        "time": "Thu Aug 23 12:15:26 2012 +0200"
      },
      "message": "Remove unused imports\n\nThere are several imports that are not used.  Remove them.\n\nChange-Id: I2ac3be66827bd68d3faedcef7d6bbf30ea01d3f2\n"
    },
    {
      "commit": "5e57234ec619d0de930333a8dde3004d1dc575d6",
      "tree": "40f4eab3f13e5b4a1ca4ff3f501539ae63f44229",
      "parents": [
        "5d016502ebc68bc054d85c98c6cdb51e0b63a1f5"
      ],
      "author": {
        "name": "Joe Hansche",
        "email": "jhansche@myyearbook.com",
        "time": "Mon Mar 05 11:41:19 2012 -0500"
      },
      "committer": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Wed Jun 13 10:34:41 2012 -0700"
      },
      "message": "Support automatically stashing local modifications during repo-rebase.\n\nCurrently repo-rebase requires that all modifications be committed\nlocally before it will allow the rebase. In high-velocity environments,\nyou may want to just pull in newer code without explicitly creating\nlocal commits, which is typically achieved using git-stash.\n\nIf called with the --auto-stash command line argument, and it is\ndetermined that the current index is dirty, the local modifications\nare stashed, and the rebase continues.  If a stash was performed, that\nstash is popped once the rebase completes.\n\nNote that there is still a possibility that the git-stash pop will\nresult in a merge conflict.\n\nChange-Id: Ibe3da96f0b4486cb7ce8d040639187e26501f6af\n"
    },
    {
      "commit": "a22f99ae41a9cdda2129c89678a6f581b0445c85",
      "tree": "73178332fc8b636f3b9c90bd68f361a1456cdd6d",
      "parents": [
        "3575b8f8bdc5f15de23db82499e0ce152f634a19"
      ],
      "author": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Thu Jul 15 17:40:41 2010 -0700"
      },
      "committer": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Thu Jul 15 17:43:02 2010 -0700"
      },
      "message": "rebase: Pass through more options\n\nPassing through --whitespace\u003dfix to rebase can be useful\nto clean up a branch prior to uploading it for review.\n\nChange-Id: Id85f1912e5e11ff9602e3b342c2fd7441abe67d7\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n"
    },
    {
      "commit": "9e426aa43231073c4a98dae3f6c16d67ab6f3b59",
      "tree": "ca0591e5569e398853ddab2a873098a505f5f96b",
      "parents": [
        "08a3f68d38eec81dfa66f9ea05080c37c863f322"
      ],
      "author": {
        "name": "Daniel Sandler",
        "email": "dsandler@android.com",
        "time": "Thu Apr 01 10:42:33 2010 -0400"
      },
      "committer": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Thu Jul 15 16:35:31 2010 -0700"
      },
      "message": "rebase: Automatically rebase branch on upstrea\n\n  Usage: repo rebase [[-i] \u003cproject\u003e...]\n\nRebases the current topic branch of the specified (or all)\nprojects against the appropriate upstream.\n\nNote: Interactive rebase is currently only supported when\nexactly one project is specified on the command line.\n\nChange-Id: I7376e35f27a6585149def82938c1ca99f36db2c4\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n"
    }
  ]
}