)]}'
{
  "commit": "f46902a800f508061322a36b1969f51a7e95df16",
  "tree": "b0865343f7fa5702bf16c7662852b45f6119c084",
  "parents": [
    "c00d28b767240ef17a0402a7d55a7a6197ce2815"
  ],
  "author": {
    "name": "David Pursehouse",
    "email": "dpursehouse@collab.net",
    "time": "Tue Oct 31 12:27:17 2017 +0900"
  },
  "committer": {
    "name": "David Pursehouse",
    "email": "dpursehouse@collab.net",
    "time": "Tue Oct 31 13:07:55 2017 +0900"
  },
  "message": "forall: Clarify expansion of REPO_ environment values with -c\n\nIf a user executes:\n\n  repo forall -c echo $REPO_PROJECT\n\nthen $REPO_NAME is expanded by the user\u0027s shell first, and passed\nas $1 to the shell that executes echo. This will either result in\nno output, or output of whatever REPO_NAME is set to in the user\u0027s\nshell. Either way, this is an unexpected result.\n\nThe correct way to do it is:\n\n  repo forall -c \u0027echo $REPO_PROJECT\u0027\n\nsuch that $REPO_NAME is passed in to the shell literally, and then\nexpanded to the value set in the environment that was passed to\nthe shell.\n\nUpdate the documentation to make this clearer.\n\nChange-Id: I713caee914172ad8d8f0fafacd27026502436f0d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2c12c55ff36a5b1c89ceaf5d7e25bd715f8eafa4",
      "old_mode": 33188,
      "old_path": "subcmds/forall.py",
      "new_id": "52eb5e28b45abc5614990126544a145ea8d2d5e4",
      "new_mode": 33188,
      "new_path": "subcmds/forall.py"
    }
  ]
}