)]}'
{
  "commit": "0454220d66581f28b9688bc1b687f52cb9561798",
  "tree": "a05a4bc3c0178898c136fb8f89b890a4c8cbe033",
  "parents": [
    "5731dfce06a19f59aa1be2bd2120584864d8983b"
  ],
  "author": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Tue May 28 12:15:43 2019 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue May 28 13:06:25 2019 -0700"
  },
  "message": "request-pull: warn if the remote object is not the same as the local one\n\nIn some cases, git request-pull might be invoked with remote and\nlocal objects that differ even though they point to the same commit.\nFor example, the remote object might be a lightweight tag\nvs. an annotated tag on the local side; or the user might have\nreworded the tag locally and forgotten to push it.\n\nWhen this happens git-request-pull will not warn, because it only\nchecks that \"git ls-remote\" returns an SHA1 that matches the local\ncommit (known as $headrev in the script).  This patch makes\ngit-request-pull retrieve the tag object SHA1 while processing\nthe \"git ls-remote\" output, so that it can be matched against the\nlocal object.\n\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0d128be7fd70c0113f972f31605119f1581326e4",
      "old_mode": 33261,
      "old_path": "git-request-pull.sh",
      "new_id": "2d0e44656cc6ca4cc0cd8b579a1ebd8798e90b5f",
      "new_mode": 33261,
      "new_path": "git-request-pull.sh"
    },
    {
      "type": "modify",
      "old_id": "c1a821a549653ab2fbb9b0b8c1c990c7bc7d0578",
      "old_mode": 33261,
      "old_path": "t/t5150-request-pull.sh",
      "new_id": "852dcd913f1e746ba4a65763ae31ee96064f3fd2",
      "new_mode": 33261,
      "new_path": "t/t5150-request-pull.sh"
    }
  ]
}