)]}'
{
  "commit": "4abf20f00439b857c34bac55176011c5612310da",
  "tree": "d92894b11431f293f768e38f625be6f2881baeeb",
  "parents": [
    "35ee755a8c43bcb3c2786522d423f006c23d32df"
  ],
  "author": {
    "name": "Ævar Arnfjörð Bjarmason",
    "email": "avarab@gmail.com",
    "time": "Thu Feb 21 20:28:48 2019 +0100"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Feb 21 20:58:19 2019 -0800"
  },
  "message": "tests: fix unportable \"\\?\" and \"\\+\" regex syntax\n\nFix widely supported but non-POSIX basic regex syntax introduced in\n[1] and [2]. On GNU, NetBSD and FreeBSD the following works:\n\n    $ echo xy \u003ef\n    $ grep \u0027xy\\?\u0027 f; echo $?\n    xy\n    0\n\nThe same goes for \"\\+\". The \"?\" and \"+\" syntax is not in the BRE\nsyntax, just in ERE, but on some implementations it can be invoked by\nprefixing the meta-operator with \"\\\", but not on OpenBSD:\n\n    $ uname -a\n    OpenBSD obsd.my.domain 6.2 GENERIC#132 amd64\n    $ grep --version\n    grep version 0.9\n    $ grep \u0027xy\\?\u0027 f; echo $?\n    1\n\nLet\u0027s fix this by moving to ERE syntax instead, where \"?\" and \"+\" are\nuniversally supported:\n\n    $ grep -E \u0027xy?\u0027 f; echo $?\n    xy\n    0\n\n1. 2ed5c8e174 (\"describe: setup working tree for --dirty\", 2019-02-03)\n2. c801170b0c (\"t6120: test for describe with a bare repository\",\n   2019-02-03)\n\nSigned-off-by: Ævar Arnfjörð Bjarmason \u003cavarab@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ee5b03ee18ada34a7b8012d219cbb63c4bb7f256",
      "old_mode": 33261,
      "old_path": "t/t6120-describe.sh",
      "new_id": "2b883d8174036b7d2246fcd89f239d7ecde049d4",
      "new_mode": 33261,
      "new_path": "t/t6120-describe.sh"
    }
  ]
}