)]}'
{
  "commit": "ebe7e28a3600f4e67e9a1781e335adb36f3f139b",
  "tree": "be7d176ae2a3e0c06db9aaf6436d6a126be74530",
  "parents": [
    "f2c6fda88624370fda1fc706a0f2ceda7d50d6ab"
  ],
  "author": {
    "name": "Sean Barag",
    "email": "sean@barag.org",
    "time": "Thu Oct 01 03:46:14 2020 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Sep 30 22:09:13 2020 -0700"
  },
  "message": "clone: validate --origin option before use\n\nProviding a bad origin name to `git clone` currently reports an\n\u0027invalid refspec\u0027 error instead of a more explicit message explaining\nthat the `--origin` option was malformed.  This behavior dates back to\nsince 8434c2f1 (Build in clone, 2008-04-27).  Reintroduce\nvalidation for the provided `--origin` option, but notably _don\u0027t_\ninclude a multi-level check (e.g. \"foo/bar\") that was present in the\noriginal `git-clone.sh`.  `git remote` allows multi-level remote names\nsince at least 46220ca100 (remote.c: Fix overtight refspec validation,\n2008-03-20), so that appears to be the desired behavior.\n\nHelped-by: Junio C Hamano \u003cgitster@pobox.com\u003e\nHelped-by: Derrick Stolee \u003cstolee@gmail.com\u003e\nHelped-by: Jeff King \u003cpeff@peff.net\u003e\nSigned-off-by: Sean Barag \u003csean@barag.org\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "258bfd65b74a9995cc2dd975fec325af3284e08e",
      "old_mode": 33188,
      "old_path": "builtin/clone.c",
      "new_id": "78364a08614f66b80146e98143733e06f5169e98",
      "new_mode": 33188,
      "new_path": "builtin/clone.c"
    }
  ]
}