)]}'
{
  "commit": "37dbf2bf0fa799530052ffd010dadbd4c01b7746",
  "tree": "9e9be8619020ba6b6de2bc28ba5da94fa69e6188",
  "parents": [
    "438c54713a7ca56fba2a7985b6563aa076b17169"
  ],
  "author": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Thu Jul 02 10:53:04 2009 -0700"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Thu Jul 02 10:53:04 2009 -0700"
  },
  "message": "Try to prevent \u0027repo sync\u0027 as a user name\n\nWhen someone copies and pastes a setup line from a web page,\nthey might actually copy \u0027repo sync\u0027 onto the clipboard and wind\nup pasting it into the \"Your Name\" prompt.  This means they will\ninitialize their client with the user name of \"repo sync\", creating\nsome rather funny looking commits later on.  For example:\n\n  To setup your source tree:\n\n    mkdir ~/code\n    cd ~/code\n    repo init -u git://....\n    repo sync\n\nIf this entire block was just blindly copy and pasted into the\nterminal, the shell won\u0027t read \"repo sync\" but \"repo init\" will.\n\nBy showing the user their full identity string, and asking them\nto confirm it before we continue, we can give the hapless user a\nchance to recover from this mistake, without unfairly harming those\nwho were actually named \u0027repo\u0027 by their parents.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fbc406e22418b1046e423ff76f5bc334b1348cd5",
      "old_mode": 33188,
      "old_path": "subcmds/init.py",
      "new_id": "75a58f11aa39d18e834f583fa11c50e5951a4d79",
      "new_mode": 33188,
      "new_path": "subcmds/init.py"
    }
  ]
}